Abundance Apis MCP Server
https://abundanceapis.com/mcp
Remote
v1.0.0
Published by abundanceapis.com — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
Try 26 utility REST APIs keylessly: NAICS classification, IP geo, email validation, currency.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 3 = 97. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 2
medium Unconstrained URL/host parameter "url" on "url_metadata"MTC-CAP-007
Tool "url_metadata" takes a URL/host parameter "url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).
Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.
Location: tool url_metadata · inputSchema.properties.url
medium Unconstrained URL/host parameter "url" on "cors_fetch"MTC-CAP-007
Tool "cors_fetch" takes a URL/host parameter "url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).
Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.
Location: tool cors_fetch · inputSchema.properties.url
Tools 7
Each tool and what it can reach — enumerated from the running server.
cors_fetchingests untrusted inputurl_metadataingests untrusted inputcurrency_convertno sensitive capabilityemail_validateno sensitive capabilityip_lookupno sensitive capabilitylist_apisno sensitive capabilitynaics_matchno sensitive capability
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.0.0 latest |
A 97/100 | 2 | 1.12.1 | 2026-07-28 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan https://abundanceapis.com/mcp --onlineMore in Communication & Collaboration
One key, 100+ models — chat with any LLM and generate video, images, speech. Free trial at 370.ai.
[](https://github.com/dealfluence/adeu) [](https://modelcontextprotocol.io/) [![License: MIT](ht
Retired compatibility stub for the AgentCanary MCP server. Daily briefs continue on X and Telegram.
A Backstage plugin that provides a chat interface for interacting with the MCP Servers.
Signal-first Bitcoin intelligence: sovereign, hiring & hashrate signals over MCP.
WhatsApp® reminders and rescheduling for Calendly. Public read-only MCP endpoint.