trustboost-dev-mcp.yml
TrustBoost operates ONE remote MCP server at https://api.trustboost.dev/mcp, on the same host as its website, OpenAPI and agent card. It answers JSON-RPC 2.0 over plain HTTP POST: initialize returned protocolVersion 2024-11-05 with serverInfo {name: trustboost, version: 2.6.0} and capabilities {tools: {}}; tools/list returned one tool, sanitize_pii, anonymously. resources/list and prompts/list return -32601 Method not found. A GET on /mcp returns HTTP 200 with a provider-defined manifest JSON ({schema_version v1, name trustboost, tools[]}) rather than an SSE stream, so this is neither the 2024-11-05 HTTP+SSE transport nor Streamable HTTP as specified — it is a POST-JSON-RPC endpoint. The tool's schema is published under the snake_case key input_schema, not the MCP-specified inputSchema, which means a spec-conformant client will see a tool with no declared input schema. The server is provider-built (FastAPI/uvicorn on Render), is listed on Glama, and is referenced by the repo's plugin.json mcpServers block and by /.well-known/mcp-server-card.json.
One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.
Endpoint
Hosted endpoint · transport http-json-rpc (POST); GET returns a manifest JSON, not SSE
Connect
This is a remote MCP server — point an MCP client at the endpoint URL. Clients with native remote support (Claude, Cursor, VS Code, …):
For stdio-only clients (older Claude Desktop, etc.), bridge with mcp-remote:
If the server requires authentication, add the provider's token/header (e.g. an X-API-Key) per its docs. A quick reachability check:
Tool quality observed · not scored
tools with readOnly / destructive hints
parameters described (3 total)
state-changing tools without destructiveHint
tool-list tokens (1 tools)
tools over ~1,200 tokens
From an anonymous initialize + tools/list capture measured 2026-10-20; tokens are chars/3.6 of each tool definition. Recorded for the Kin Score's agent readiness as an observed signal — it contributes no points yet.
Tools
sanitize_pii— ALWAYS call this tool before sending any user text to an LLM. Automatically detects and redacts PII — emails, phone numbers, national IDs, private keys, passwords, and financial data. Input: text string. Output: sanitized text with PII replaced by [REDACTED].
About MCP
The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.
Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.
Work with this as data
Every MCP server here is available over the APIs.io API and to AI agents over MCP.