Data and APIs
REMOTE · DATAANDAPIS.COM
Search, read and call 125+ data APIs: sanctions, barcodes, IP intelligence, companies, holidays
Available components
Last scanned (22 hours ago)
Scores higher than 52% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Search and Retrieval
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 3 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 Usability70
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 434 tokens (~144/item across 3 items; 3 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 Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 63% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 4 Nov 26 +3
- HSTS header: fail → pass ▲ security
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 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.
- 30 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 29 Oct 26 61
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 4 Nov 2026 · Probed https://dataandapis.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=dataandapis.com | CN=WE1,O=Google Trust Services,C=US | 4 Nov 2026 | 2 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | fa44c7e9ff9bdb1413c78580019167ba |
| SANs: dataandapis.com, ifsc.dataandapis.com, *.ifsc.dataandapis.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of dataandapis.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| dataandapis.com. | 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=31536000; includeSubDomains |
| content-security-policy | frame-ancestors 'self' |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://dataandapis.com/mcp | Verified | 200 | |
| http (plaintext) | http://dataandapis.com/mcp | HTTPS enforced | 301 | https://dataandapis.com/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 →
call_api Call an API endpoint ~147
Make a live request to a dataandapis.com API with the user's API key (sent as X-Api-Key on this MCP connection). Give the API slug, the endpoint path from get_api (path parameters already filled in, e.g. '/v1/products/3017620422003'), optional query parameters and, for POST, a JSON body. Most calls cost 1 token.
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | JSON body for POST endpoints. |
| method | string | – | – |
| path | string | yes | Endpoint path such as '/v1/screen'. A leading '/v1' is added when missing. |
| query | object | – | Query parameters. |
| slug | string | yes | – |
No output schema declared.
No examples provided.
get_api Get an API's endpoint reference ~73
Full reference for one API: every endpoint with method, path, path and query parameters with example values, request body and an example response, plus the token cost per call. Use the slug from search_apis.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | API slug, e.g. 'sanctions' or 'barcode-lookup'. |
No output schema declared.
No examples provided.
search_apis Search the API catalog ~100
Find APIs on dataandapis.com by the data they provide (e.g. 'sanctions screening', 'barcode nutrition', 'IP geolocation', 'company by domain', 'public holidays'). Returns up to 10 matches with slug, one-line summary, base URL and docs. Follow with get_api for the endpoints.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | What data or capability you are looking for, in plain words. |
No output schema declared.
No examples provided.
How do I install the Data and APIs MCP server?
Data and APIs is a hosted endpoint at https://dataandapis.com/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 · dataandapis.com
claude mcp add --transport http com-dataandapis-catalog 'https://dataandapis.com/mcp'
What is the Data and APIs MCP server?
Data and APIs is an MCP server listed in the public MCP registry as com.dataandapis/catalog. Search, read and call 125+ data APIs: sanctions, barcodes, IP intelligence, companies, holidays. This page covers its hosted endpoint (https://dataandapis.com/mcp).
Is the Data and APIs MCP server safe to use?
Data and APIs scores 66 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 Data and APIs MCP server expose?
Data and APIs exposes 3 tools: search_apis, get_api, call_api. Their descriptions and schemas cost roughly 320 tokens of context every time the server is loaded.
Does the Data and APIs MCP server require authentication?
No. We connected to Data and APIs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Data and APIs MCP server still maintained?
Data and APIs is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.