_ registry / mcp streamable-http · checked 2h ago

raintree-technology-public

https://raintree.technology

Registry code: 32fd73c1a710fc28

api record

Anonymous read-only access to Raintree Technology. Public company, portfolio, research, and contact facts only. Tools never send messages or expose private company records.

endpoint
https://raintree.technology/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is raintree-technology-public live?
Yes — it answered the hub's last check (checked 2h ago). It answered 95% of checks over the last 30 days.
Is raintree-technology-public free to use?
Yes — the hub reached it with no key and no payment.
What tools does raintree-technology-public have?
7 tools: search_projects, get_project, search_research, list_open_source_projects, get_company_capabilities, list_products, get_contact_options.
Is raintree-technology-public safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
94.8%

90 days 95%· all time 95%

latency
743ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 358 checks · signed record
  • down → live
  • degraded → down· HTTP 500
  • live → degraded· HTTP 500
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
productivity & business
used for
  • get company description and portfolio
  • list public products and open-source projects
  • search company research
  • get contact options
takes → gives
text → text, data
tools
7 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 7 tools
4 open 3 never probed 4 of 7 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_open_source_projects reads open 16h ago

    Use this when an agent needs to list Raintree Technology's public open-source projects and repositories.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {},
  "additionalProperties": false
}
    arguments 6 lines
  • get_company_capabilities reads open 16h ago

    Use this when an agent needs to get Raintree Technology's public company description, sectors, and portfolio scope.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {},
  "additionalProperties": false
}
    arguments 6 lines
  • list_products reads open 13h ago

    Use this when an agent needs to list related products built by Raintree Technology’s founder.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {},
  "additionalProperties": false
}
    arguments 6 lines
  • get_contact_options reads open 16h ago

    Use this when an agent needs to return public contact options without sending a message or submitting a form.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {},
  "additionalProperties": false
}
    arguments 6 lines
  • search_projects reads unknown 13h ago

    Use this when an agent needs to search Raintree Technology's open-source tools and related founder products.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1,
      "description": "Case-insensitive public search query"
    }
  },
  "additionalProperties": false
}
    arguments 16 lines
  • get_project reads unknown 13h ago

    Use this when an agent needs to get one public Raintree Technology project by canonical identifier.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "maxLength": 80,
      "minLength": 1,
      "description": "Canonical public project identifier"
    }
  },
  "additionalProperties": false
}
    arguments 16 lines
  • search_research reads unknown 9h ago

    Use this when an agent needs to search public Raintree Technology research.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string",
      "maxLength": 200,
      "minLength": 1,
      "description": "Case-insensitive public search query"
    }
  },
  "additionalProperties": false
}
    arguments 16 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 32fd73c1a710fc28.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/32fd73c1a710fc28/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/32fd73c1a710fc28/badge.svg)](https://brick.blue/agent/32fd73c1a710fc28?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.