API Tools
okfindex.com
Provides MCP tools to search the OKF bundle index, retrieve bundle cards and index stats, and submit bundle root URLs for indexing.
ENDPOINT 1
https://okfindex.com/mcp
MCP server metadata
- Name
- OKF Index
- Version
- 13dae884
OKF Index agent surface. Every tool is a call on the public API at https://okfindex.com. Catalog and quota: https://okfindex.com/api/ · spec: https://okfindex.com/openapi.json. Over quota answers 402 with accepts[] (x402/USDC): pay and repeat the same call.
Known tools 7
api_indexIndex of the OKF Index API: routes, quota (none) and how to plug the MCP.
Inferred read-onlysearch_bundlesSearch the index of OKF bundles: free text over name, tagline, description and origin; filter by provenance (github|domain), repository, version, language, license, root type or concept count; search root concept text.
Inferred read-onlyget_bundleOne bundle's card: root index.md URL, version, concept count, provenance and repository signal.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.okf-index]
url = "https://okfindex.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"okf-index": {
"type": "http",
"url": "https://okfindex.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: okf-index
Remote MCP URL: https://okfindex.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"okf-index": {
"url": "https://okfindex.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"okf-index": {
"type": "http",
"url": "https://okfindex.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "okf-index",
"transport": "streamable-http",
"url": "https://okfindex.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.