Raintree Technology
REMOTE · RAINTREE.TECHNOLOGY · SCANNED SEP 20
Anonymous public tools for Raintree Technology. See the published agent boundary before use.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 268 tokens (~38/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management61
- Stability check failed: schema churn in the 23 days we've observed: 1 tool removals, 0 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Raintree Technology MCP server?
Raintree Technology is a hosted endpoint at https://raintree.technology/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · raintree.technology
claude mcp add --transport http technology-raintree-public 'https://raintree.technology/mcp'
{
"mcpServers": {
"technology-raintree-public": {
"url": "https://raintree.technology/mcp"
}
}
} {
"servers": {
"technology-raintree-public": {
"type": "http",
"url": "https://raintree.technology/mcp"
}
}
} [mcp_servers.technology-raintree-public] url = "https://raintree.technology/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"technology-raintree-public": {
"type": "remote",
"url": "https://raintree.technology/mcp",
"enabled": true
}
}
} openclaw mcp add technology-raintree-public --url 'https://raintree.technology/mcp' --transport streamable-http
mcp_servers:
technology-raintree-public:
url: "https://raintree.technology/mcp" {
"McpServers": {
"technology-raintree-public": {
"Transport": "http",
"Url": "https://raintree.technology/mcp"
}
}
} assistant mcp add technology-raintree-public -t streamable-http -u 'https://raintree.technology/mcp'
{
"mcpServers": {
"technology-raintree-public": {
"type": "http",
"url": "https://raintree.technology/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 54 to 57.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 51.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 41 to 44.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 34 to 37.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 31.
- 10 Sept 26 −2
- Stability: 0.40 → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “search_writing” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- New tool “search_research” functional
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://raintree.technology/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=raintree.technology | CN=YR1,O=Let's Encrypt,C=US | 20 Aug 2026 | 18 Nov 2026 | RSA 2048 | SHA256-RSA | 5cc393ba4747af2c694559036fb0a810d98 |
| SANs: raintree.technology | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of raintree.technology. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| technology. | present | 27175 | 8 | Verified |
| raintree.technology. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' https://va.vercel-scripts.com 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data: https: blob:; font-src 'self' data:; media-src 'self'; connect-src 'self' https://vitals.vercel-insights.com https://va.vercel-scripts.com; worker-src 'self' blob:; manifest-src 'self'; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), browsing-topics=(), payment=(), usb=(), bluetooth=(), serial=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://raintree.technology/mcp | Verified | 200 | |
| http (plaintext) | http://raintree.technology/mcp | HTTPS enforced | 308 | https://raintree.technology/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_company_capabilities Get Company Capabilities ~33
Use this when an agent needs to get Raintree Technology's public company description, sectors, and portfolio scope.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_contact_options Get Contact Options ~29
Use this when an agent needs to return public contact options without sending a message or submitting a form.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
get_project Get Project ~39
Use this when an agent needs to get one public Raintree Technology project by canonical identifier.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Canonical public project identifier |
Structured output declared, but exposes no named fields.
No examples provided.
list_open_source_projects List Open Source Projects ~30
Use this when an agent needs to list Raintree Technology's public open-source projects and repositories.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
list_products List Products ~24
Use this when an agent needs to list Raintree Technology's public products.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
search_projects Search Projects ~41
Use this when an agent needs to search Raintree Technology's public product and open-source portfolio.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Case-insensitive public search query |
Structured output declared, but exposes no named fields.
No examples provided.
search_research Search Research ~37
Use this when an agent needs to search public Raintree Technology research.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Case-insensitive public search query |
Structured output declared, but exposes no named fields.
No examples provided.
What is the Raintree Technology MCP server?
Raintree Technology is an MCP server listed in the public MCP registry as technology.raintree/public. Anonymous public tools for Raintree Technology. See the published agent boundary before use. This page covers its hosted endpoint (https://raintree.technology/mcp).
Is the Raintree Technology MCP server safe to use?
Raintree Technology scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Raintree Technology MCP server expose?
Raintree Technology exposes 7 tools: search_projects, get_project, list_products, list_open_source_projects, search_research, and 2 more. Their descriptions and schemas cost roughly 233 tokens of context every time the server is loaded.
Does the Raintree Technology MCP server require authentication?
No. We connected to Raintree Technology without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Raintree Technology MCP server still maintained?
Raintree Technology is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.