mcp-public-apis
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_apisA | Search the public-apis list by keyword, category, auth type, and HTTPS support. |
| get_categoriesA | Returns all available API categories with the number of APIs in each. |
| get_api_detailA | Get full details about a specific API by name. |
| probe_apiB | Makes a safe live HTTP GET request to a given API endpoint and returns the response status, shape, and latency. |
| compare_apisA | Compare all APIs within a category side by side, with a summary of auth and HTTPS support. |
| find_no_auth_apisB | Returns APIs that require zero authentication, optionally filtered by category. |
| generate_snippetB | Generates ready-to-use curl, fetch, and axios code snippets for calling a given API endpoint. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool has a clear, distinct purpose: comparing APIs, finding auth-free ones, generating code snippets, getting details, listing categories, probing endpoints, and searching. No overlap.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., compare_apis, find_no_auth_apis, generate_snippet), making them predictable and easy to understand.
With 7 tools, the set is well-scoped for browsing and testing public APIs. Each tool adds distinct value without redundancy or over-engineering.
The tool set covers the full workflow: discovery (search, categories, detail), analysis (compare, no-auth filter), testing (probe), and code generation (snippet). No obvious gaps for a read-only API directory.