Library
REMOTE · LIBRARYMCP.VERCEL.APP · SCANNED SEP 20
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 → Why this is hard to 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 Usability79
- AI-judged instruction clarity (excellent).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 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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 Library MCP server?
Library is a hosted endpoint at https://librarymcp.vercel.app/api/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 · librarymcp.vercel.app
claude mcp add --transport http spacemandomains-library-mcp 'https://librarymcp.vercel.app/api/mcp'
{
"mcpServers": {
"spacemandomains-library-mcp": {
"url": "https://librarymcp.vercel.app/api/mcp"
}
}
} {
"servers": {
"spacemandomains-library-mcp": {
"type": "http",
"url": "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": {
"Transport": "http",
"Url": "https://librarymcp.vercel.app/api/mcp"
}
}
} assistant mcp add spacemandomains-library-mcp -t streamable-http -u '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.
- 15 Sept 26 +56
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: 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. security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 6 Sept 26 −56
- Endpoint reachability: reachable → not serving MCP ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.97 → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 −1
- Stability: pass → 0.93 functional
- 26 Aug 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 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
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://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 | 29 Aug 2026 | 27 Nov 2026 | RSA 2048 | SHA256-RSA | f7911168ffa7d0f4135e24792e7a52a8 |
| 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 |
Background: What to check on a remote MCP endpoint →
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
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. 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 →
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.
What is the Library MCP server?
Library is an MCP server listed in the public MCP registry as io.github.Spacemandomains/library-mcp. Search and discover 25,000+ MCP servers across all major registries. Connect and pay autonomously. This page covers its hosted endpoint (https://librarymcp.vercel.app/api/mcp).
Is the Library MCP server safe to use?
Library scores 81 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 Library MCP server expose?
Library exposes 4 tools: search, inspect, catalog, checkout. Their descriptions and schemas cost roughly 503 tokens of context every time the server is loaded.
Does the Library MCP server require authentication?
No. We connected to Library without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Library MCP server still maintained?
Library 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.