MCP Trust Index
REMOTE · STAAS.FUND · SCANNED SEP 24
Curated, trust-first index of vetted MCP servers — scored tiers, monthly re-verified. Read-only.
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 462 tokens (~92/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the MCP Trust Index server?
MCP Trust Index is a hosted endpoint at https://staas.fund/mcp/server, 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 · staas.fund
claude mcp add --transport http fund-staas-mcp-trust-index 'https://staas.fund/mcp/server'
{
"mcpServers": {
"fund-staas-mcp-trust-index": {
"url": "https://staas.fund/mcp/server"
}
}
} {
"servers": {
"fund-staas-mcp-trust-index": {
"type": "http",
"url": "https://staas.fund/mcp/server"
}
}
} [mcp_servers.fund-staas-mcp-trust-index] url = "https://staas.fund/mcp/server"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"fund-staas-mcp-trust-index": {
"type": "remote",
"url": "https://staas.fund/mcp/server",
"enabled": true
}
}
} openclaw mcp add fund-staas-mcp-trust-index --url 'https://staas.fund/mcp/server' --transport streamable-http
mcp_servers:
fund-staas-mcp-trust-index:
url: "https://staas.fund/mcp/server" {
"McpServers": {
"fund-staas-mcp-trust-index": {
"Transport": "http",
"Url": "https://staas.fund/mcp/server"
}
}
} assistant mcp add fund-staas-mcp-trust-index -t streamable-http -u 'https://staas.fund/mcp/server'
{
"mcpServers": {
"fund-staas-mcp-trust-index": {
"type": "http",
"url": "https://staas.fund/mcp/server"
}
}
} 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.
- 20 Sept 26 +1
- Stability: 0.97 → pass security
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 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 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 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 24 Sept 2026 · Probed https://staas.fund/mcp/server
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=staas.fund | CN=WE1,O=Google Trust Services,C=US | 17 Aug 2026 | 15 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | c05cfa781afa5bef0e1ed2e7d7d3d7bc |
| SANs: staas.fund | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of staas.fund. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| fund. | present | 58270 | 8 | Verified |
| staas.fund. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://staas.fund/mcp/server | Verified | 200 | |
| http (plaintext) | http://staas.fund/mcp/server | HTTPS enforced | 301 | https://staas.fund/mcp/server |
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_changelog Get the index changelog ~28
Public log of every addition, removal, and re-score on the Trust Index, with reasoning.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_rubric Get the evaluation methodology ~41
The full MCP Trust Index methodology as markdown: the 5 gates every server must pass, the 4 scoring dimensions, trust tiers, and editorial policies.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_server Get one server record ~67
Full Trust Index record for a single listed server: score, tier, publisher, description with caveats, category, install command, and links. Name is matched case-insensitively.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Server name, e.g. "Playwright" or "context7" |
No output schema declared.
No examples provided.
get_watchlist Get unscored & watched servers ~48
Servers the Index deliberately does not score: closed-source hosted vendor endpoints and platform-native MCP capabilities (no inspectable code to gate), plus open servers being watched that have not yet passed the gates.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_servers Search the Trust Index ~128
Search the MCP Trust Index for vetted MCP servers. Filter by free-text query (matched against name, publisher, description, and category), category, and/or trust tier. Returns compact records sorted by score. Call with no arguments to list the entire index.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | One of: Database, Developer Tools, File Systems, Search, Productivity, CRM/Business, Cloud, Monitoring, AI/ML |
| query | string | – | Free-text filter, e.g. "postgres", "browser", "search" |
| tier | string | – | enterprise-verified | recommended | emerging |
No output schema declared.
No examples provided.
What is the MCP Trust Index server?
MCP Trust Index is listed in the public MCP registry as fund.staas/mcp-trust-index. Curated, trust-first index of vetted MCP servers, scored tiers, monthly re-verified. Read-only. This page covers its hosted endpoint (https://staas.fund/mcp/server).
Is the MCP Trust Index server safe to use?
MCP Trust Index scores 78 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 MCP Trust Index server expose?
MCP Trust Index exposes 5 tools: search_servers, get_server, get_rubric, get_watchlist, get_changelog. Their descriptions and schemas cost roughly 312 tokens of context every time the server is loaded.
Does the MCP Trust Index server require authentication?
No. We connected to MCP Trust Index without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MCP Trust Index server still maintained?
MCP Trust Index is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.