Library
REMOTE · LIBRARYMCP.VERCEL.APP · SCANNED AUG 3
Search and discover 25,000+ MCP servers across all major registries. Connect and pay autonomously.
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 →
Endpoint Security63
- 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 4 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
- 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 Usability71
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 503 tokens (~125/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · librarymcp.vercel.app
claude mcp add --transport http spacemandomains-library-mcp https://librarymcp.vercel.app/api/mcp
[mcp_servers.spacemandomains-library-mcp] url = "https://librarymcp.vercel.app/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"spacemandomains-library-mcp": {
"type": "remote",
"url": "https://librarymcp.vercel.app/api/mcp",
"enabled": true
}
}
} openclaw mcp add spacemandomains-library-mcp --url https://librarymcp.vercel.app/api/mcp --transport streamable-http
mcp_servers:
spacemandomains-library-mcp:
url: "https://librarymcp.vercel.app/api/mcp" {
"mcpServers": {
"spacemandomains-library-mcp": {
"type": "http",
"url": "https://librarymcp.vercel.app/api/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.
- 2 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 64
First indexed and scored.
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 3 Aug 2026 · Probed https://librarymcp.vercel.app/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.vercel.app | CN=WR1,O=Google Trust Services,C=US | 28 Jun 2026 | 26 Sept 2026 | RSA 2048 | SHA256-RSA | b1c2b607df94f28513779ae26fecf92f |
| SANs: *.vercel.app | ||||||
| CN=WR1,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7fd9e2c2d2048a0474b627a26d0868a7 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
DNSSEC insecure
Validation of librarymcp.vercel.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| vercel.app. | 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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://librarymcp.vercel.app/api/mcp | Verified | 200 | |
| http (plaintext) | http://librarymcp.vercel.app/api/mcp | HTTPS enforced | 308 | https://librarymcp.vercel.app/api/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.
catalog Registry Catalog ~21
List all registries being searched with live status and total server counts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
checkout Checkout / Pay for MCP Server ~106
Detect payment protocol for any MCP server and route to the correct payment execution. Supports x402 (USDC on Base), MPP (Stripe), and prepaid API keys.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | — | fund | execute | check |
| agent_id | string | — | Optional identifier for this agent |
| amount | number | — | USD amount to fund if prepaid (default 5) |
| endpoint | string | yes | MCP server endpoint URL |
| payload | object | — | Request body for execute action |
No output schema declared.
No examples provided.
inspect Inspect MCP Server ~52
Get full metadata for any MCP server. Accepts reverse-DNS name, endpoint URL, or plain keyword. Includes payment protocol detection.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | Reverse-DNS name, endpoint URL, or plain keyword |
No output schema declared.
No examples provided.
search Search MCP Servers ~324
Search MCP servers by server title/name, description, or by the tools they provide. Accepts natural language capability queries like 'send emails', 'search the web', 'create pull requests', or direct server names like 'GitHub' or 'Stripe'. Results are ranked by relevance: title match first, then tool name match, then description. Each result includes the server's tool list so you can confirm it does what you need. Set limit based on the type of request you received: - Prompting (general/exploratory — user is browsing or asking broadly): use 20-30 - Task assignment (user delegated a goal for you to execute autonomously): use 10-15 - Instruction/directive (specific command with a clear target server in mind): use 3-5
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | — | Max total results (default 20, max 50). Use 20-30 for exploratory prompts, 10-15 for delegated tasks, 3-5 for specific directives. |
| payment_protocol | array | — | Filter results to servers using specific payment protocols. x402 queries x402.direct, mpp queries mppscan.com. |
| query | string | yes | Server name/title (e.g. 'GitHub', 'Stripe') OR a task/capability (e.g. 'send emails', 'search the web', 'create pull requests', 'analyze crypto prices') |
| sources | array | — | Filter to specific sources: official-registry, glama, mcpso, x402direct, mppscan |
No output schema declared.
No examples provided.