Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Ready APIs

REMOTE · READYAPIS.COM · SCANNED SEP 29

135 MCP tools: geo, email, phone, company, DNS, FX, equities, weather, tax, econ, intel — one key.

Available components

+3 this week 86 Trust /100
Trust breakdown (7 categories)

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 Security80
Transport & Reachability100
Schema Quality & AI Usability84
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 11448 tokens (~63/item across 181 items; 135 tools + 46 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management99
  • Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 2 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage83
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 49% 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 135 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 137 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
Install

How do I install the Ready APIs MCP server?

Ready APIs is a hosted endpoint at https://readyapis.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 · readyapis.com

# add to Claude Code
claude mcp add --transport http com-readyapis-api 'https://readyapis.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-readyapis-api": {
      "url": "https://readyapis.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-readyapis-api": {
      "type": "http",
      "url": "https://readyapis.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-readyapis-api]
url = "https://readyapis.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-readyapis-api": {
      "type": "remote",
      "url": "https://readyapis.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-readyapis-api --url 'https://readyapis.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-readyapis-api:
    url: "https://readyapis.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-readyapis-api": {
      "Transport": "http",
      "Url": "https://readyapis.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-readyapis-api -t streamable-http -u 'https://readyapis.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-readyapis-api": {
      "type": "http",
      "url": "https://readyapis.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 29 Sept 26 0
    • A breaking change shipped without a version bump: still 1.0.0 ▼ security
    • Tool “jobs_companies_hiring” rewrote its description, which is the text the model reads security
    • Tool “jobs_related_skills” rewrote its description, which is the text the model reads security
    • Tool “jobs_remote_trends” rewrote its description, which is the text the model reads security
    • Tool “jobs_role_skills” rewrote its description, which is the text the model reads security
    • Tool “jobs_salary_signals” rewrote its description, which is the text the model reads security
    • Tool “jobs_skill_trends” rewrote its description, which is the text the model reads security
    • “jobs_companies_hiring” dropped the required parameter “location” ▼ functional
    • “jobs_remote_trends” dropped the required parameter “role” ▼ functional
    • “jobs_companies_hiring” added an optional parameter “limit” cosmetic
    • “jobs_companies_hiring” added an optional parameter “skill” cosmetic
    • “jobs_companies_hiring” added an optional parameter “title” cosmetic
    • “jobs_related_skills” added an optional parameter “limit” cosmetic
    • “jobs_remote_trends” added an optional parameter “skill” cosmetic
    • “jobs_remote_trends” added an optional parameter “title” cosmetic
    • “jobs_role_skills” added an optional parameter “limit” cosmetic
    • “jobs_salary_signals” added an optional parameter “skill” cosmetic
    • “jobs_skill_trends” added an optional parameter “location” cosmetic
    • “jobs_related_skills” reworded the description of “skill” cosmetic
    • “jobs_role_skills” reworded the description of “title” cosmetic
    • “jobs_salary_signals” reworded the description of “title” cosmetic
    • “jobs_skill_trends” reworded the description of “skill” cosmetic
    • “jobs_companies_hiring” dropped the optional parameter “role” cosmetic
    • “jobs_salary_signals” made “title” optional cosmetic
    • Tool “jobs_companies_hiring” changed its title: Jobs Companies Hiring → Top Hiring Companies cosmetic
    • Tool “jobs_related_skills” changed its title: Jobs Related Skills → Related Skills cosmetic
    • Tool “jobs_remote_trends” changed its title: Jobs Remote Trends → Remote-Work Trends cosmetic
    • Tool “jobs_role_skills” changed its title: Jobs Role Skills → Role Skills cosmetic
    • Tool “jobs_salary_signals” changed its title: Jobs Salary Signals → Salary Signals cosmetic
    • Tool “jobs_skill_trends” changed its title: Jobs Skill Trends → Job Skill Trends cosmetic
  • 28 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 0
    • A breaking change shipped without a version bump: still 1.0.0 ▼ security
    • Tool “jobs_companies_hiring” rewrote its description, which is the text the model reads security
    • Tool “jobs_related_skills” rewrote its description, which is the text the model reads security
    • Tool “jobs_remote_trends” rewrote its description, which is the text the model reads security
    • Tool “jobs_role_skills” rewrote its description, which is the text the model reads security
    • Tool “jobs_salary_signals” rewrote its description, which is the text the model reads security
    • Tool “jobs_skill_trends” rewrote its description, which is the text the model reads security
    • “jobs_companies_hiring” dropped the required parameter “location” ▼ functional
    • “jobs_remote_trends” dropped the required parameter “role” ▼ functional
    • “jobs_companies_hiring” added an optional parameter “limit” cosmetic
    • “jobs_companies_hiring” added an optional parameter “skill” cosmetic
    • “jobs_companies_hiring” added an optional parameter “title” cosmetic
    • “jobs_related_skills” added an optional parameter “limit” cosmetic
    • “jobs_remote_trends” added an optional parameter “skill” cosmetic
    • “jobs_remote_trends” added an optional parameter “title” cosmetic
    • “jobs_role_skills” added an optional parameter “limit” cosmetic
    • “jobs_salary_signals” added an optional parameter “skill” cosmetic
    • “jobs_skill_trends” added an optional parameter “location” cosmetic
    • “jobs_related_skills” reworded the description of “skill” cosmetic
    • “jobs_role_skills” reworded the description of “title” cosmetic
    • “jobs_salary_signals” reworded the description of “title” cosmetic
    • “jobs_skill_trends” reworded the description of “skill” cosmetic
    • “jobs_companies_hiring” dropped the optional parameter “role” cosmetic
    • “jobs_salary_signals” made “title” optional cosmetic
    • Tool “jobs_companies_hiring” changed its title: Jobs Companies Hiring → Top Hiring Companies cosmetic
    • Tool “jobs_related_skills” changed its title: Jobs Related Skills → Related Skills cosmetic
    • Tool “jobs_remote_trends” changed its title: Jobs Remote Trends → Remote-Work Trends cosmetic
    • Tool “jobs_role_skills” changed its title: Jobs Role Skills → Role Skills cosmetic
    • Tool “jobs_salary_signals” changed its title: Jobs Salary Signals → Salary Signals cosmetic
    • Tool “jobs_skill_trends” changed its title: Jobs Skill Trends → Job Skill Trends cosmetic
  • 26 Sept 26 +1
    • A breaking change shipped without a version bump: still 1.0.0 ▼ security
    • Tool “jobs_companies_hiring” rewrote its description, which is the text the model reads security
    • Tool “jobs_related_skills” rewrote its description, which is the text the model reads security
    • Tool “jobs_remote_trends” rewrote its description, which is the text the model reads security
    • Tool “jobs_role_skills” rewrote its description, which is the text the model reads security
    • Tool “jobs_salary_signals” rewrote its description, which is the text the model reads security
    • Tool “jobs_skill_trends” rewrote its description, which is the text the model reads security
    • “jobs_companies_hiring” dropped the required parameter “location” ▼ functional
    • “jobs_remote_trends” dropped the required parameter “role” ▼ functional
    • “jobs_companies_hiring” added an optional parameter “limit” cosmetic
    • “jobs_companies_hiring” added an optional parameter “skill” cosmetic
    • “jobs_companies_hiring” added an optional parameter “title” cosmetic
    • “jobs_related_skills” added an optional parameter “limit” cosmetic
    • “jobs_remote_trends” added an optional parameter “skill” cosmetic
    • “jobs_remote_trends” added an optional parameter “title” cosmetic
    • “jobs_role_skills” added an optional parameter “limit” cosmetic
    • “jobs_salary_signals” added an optional parameter “skill” cosmetic
    • “jobs_skill_trends” added an optional parameter “location” cosmetic
    • “jobs_related_skills” reworded the description of “skill” cosmetic
    • “jobs_role_skills” reworded the description of “title” cosmetic
    • “jobs_salary_signals” reworded the description of “title” cosmetic
    • “jobs_skill_trends” reworded the description of “skill” cosmetic
    • “jobs_companies_hiring” dropped the optional parameter “role” cosmetic
    • “jobs_salary_signals” made “title” optional cosmetic
    • Tool “jobs_companies_hiring” changed its title: Jobs Companies Hiring → Top Hiring Companies cosmetic
    • Tool “jobs_related_skills” changed its title: Jobs Related Skills → Related Skills cosmetic
    • Tool “jobs_remote_trends” changed its title: Jobs Remote Trends → Remote-Work Trends cosmetic
    • Tool “jobs_role_skills” changed its title: Jobs Role Skills → Role Skills cosmetic
    • Tool “jobs_salary_signals” changed its title: Jobs Salary Signals → Salary Signals cosmetic
    • Tool “jobs_skill_trends” changed its title: Jobs Skill Trends → Job Skill Trends cosmetic
  • 25 Sept 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
  • 24 Sept 26 +1
    • A breaking change shipped without a version bump: still 1.0.0 ▼ security
    • Tool “jobs_companies_hiring” rewrote its description, which is the text the model reads security
    • Tool “jobs_related_skills” rewrote its description, which is the text the model reads security
    • Tool “jobs_remote_trends” rewrote its description, which is the text the model reads security
    • Tool “jobs_role_skills” rewrote its description, which is the text the model reads security
    • Tool “jobs_salary_signals” rewrote its description, which is the text the model reads security
    • Tool “jobs_skill_trends” rewrote its description, which is the text the model reads security
    • “jobs_companies_hiring” dropped the required parameter “location” ▼ functional
    • “jobs_remote_trends” dropped the required parameter “role” ▼ functional
    • “jobs_companies_hiring” added an optional parameter “limit” cosmetic
    • “jobs_companies_hiring” added an optional parameter “skill” cosmetic
    • “jobs_companies_hiring” added an optional parameter “title” cosmetic
    • “jobs_related_skills” added an optional parameter “limit” cosmetic
    • “jobs_remote_trends” added an optional parameter “skill” cosmetic
    • “jobs_remote_trends” added an optional parameter “title” cosmetic
    • “jobs_role_skills” added an optional parameter “limit” cosmetic
    • “jobs_salary_signals” added an optional parameter “skill” cosmetic
    • “jobs_skill_trends” added an optional parameter “location” cosmetic
    • “jobs_related_skills” reworded the description of “skill” cosmetic
    • “jobs_role_skills” reworded the description of “title” cosmetic
    • “jobs_salary_signals” reworded the description of “title” cosmetic
    • “jobs_skill_trends” reworded the description of “skill” cosmetic
    • “jobs_companies_hiring” dropped the optional parameter “role” cosmetic
    • “jobs_salary_signals” made “title” optional cosmetic
    • Tool “jobs_companies_hiring” changed its title: Jobs Companies Hiring → Top Hiring Companies cosmetic
    • Tool “jobs_related_skills” changed its title: Jobs Related Skills → Related Skills cosmetic
    • Tool “jobs_remote_trends” changed its title: Jobs Remote Trends → Remote-Work Trends cosmetic
    • Tool “jobs_role_skills” changed its title: Jobs Role Skills → Role Skills cosmetic
    • Tool “jobs_salary_signals” changed its title: Jobs Salary Signals → Salary Signals cosmetic
    • Tool “jobs_skill_trends” changed its title: Jobs Skill Trends → Job Skill Trends cosmetic
  • 23 Sept 26 0
    • A breaking change shipped without a version bump: still 1.0.0 ▼ security
    • Tool “jobs_companies_hiring” rewrote its description, which is the text the model reads security
    • Tool “jobs_related_skills” rewrote its description, which is the text the model reads security
    • Tool “jobs_remote_trends” rewrote its description, which is the text the model reads security
    • Tool “jobs_role_skills” rewrote its description, which is the text the model reads security
    • Tool “jobs_salary_signals” rewrote its description, which is the text the model reads security
    • Tool “jobs_skill_trends” rewrote its description, which is the text the model reads security
    • “jobs_companies_hiring” dropped the required parameter “location” ▼ functional
    • “jobs_remote_trends” dropped the required parameter “role” ▼ functional
    • “jobs_companies_hiring” added an optional parameter “limit” cosmetic
    • “jobs_companies_hiring” added an optional parameter “skill” cosmetic
    • “jobs_companies_hiring” added an optional parameter “title” cosmetic
    • “jobs_related_skills” added an optional parameter “limit” cosmetic
    • “jobs_remote_trends” added an optional parameter “skill” cosmetic
    • “jobs_remote_trends” added an optional parameter “title” cosmetic
    • “jobs_role_skills” added an optional parameter “limit” cosmetic
    • “jobs_salary_signals” added an optional parameter “skill” cosmetic
    • “jobs_skill_trends” added an optional parameter “location” cosmetic
    • “jobs_related_skills” reworded the description of “skill” cosmetic
    • “jobs_role_skills” reworded the description of “title” cosmetic
    • “jobs_salary_signals” reworded the description of “title” cosmetic
    • “jobs_skill_trends” reworded the description of “skill” cosmetic
    • “jobs_companies_hiring” dropped the optional parameter “role” cosmetic
    • “jobs_salary_signals” made “title” optional cosmetic
    • Tool “jobs_companies_hiring” changed its title: Jobs Companies Hiring → Top Hiring Companies cosmetic
    • Tool “jobs_related_skills” changed its title: Jobs Related Skills → Related Skills cosmetic
    • Tool “jobs_remote_trends” changed its title: Jobs Remote Trends → Remote-Work Trends cosmetic
    • Tool “jobs_role_skills” changed its title: Jobs Role Skills → Role Skills cosmetic
    • Tool “jobs_salary_signals” changed its title: Jobs Salary Signals → Salary Signals cosmetic
    • Tool “jobs_skill_trends” changed its title: Jobs Skill Trends → Job Skill Trends cosmetic
  • 22 Sept 26 +1
    • A breaking change shipped without a version bump: still 1.0.0 ▼ security
    • Tool “jobs_companies_hiring” rewrote its description, which is the text the model reads security
    • Tool “jobs_related_skills” rewrote its description, which is the text the model reads security
    • Tool “jobs_remote_trends” rewrote its description, which is the text the model reads security
    • Tool “jobs_role_skills” rewrote its description, which is the text the model reads security
    • Tool “jobs_salary_signals” rewrote its description, which is the text the model reads security
    • Tool “jobs_skill_trends” rewrote its description, which is the text the model reads security
    • “jobs_companies_hiring” dropped the required parameter “location” ▼ functional
    • “jobs_remote_trends” dropped the required parameter “role” ▼ functional
    • “jobs_companies_hiring” added an optional parameter “limit” cosmetic
    • “jobs_companies_hiring” added an optional parameter “skill” cosmetic
    • “jobs_companies_hiring” added an optional parameter “title” cosmetic
    • “jobs_related_skills” added an optional parameter “limit” cosmetic
    • “jobs_remote_trends” added an optional parameter “skill” cosmetic
    • “jobs_remote_trends” added an optional parameter “title” cosmetic
    • “jobs_role_skills” added an optional parameter “limit” cosmetic
    • “jobs_salary_signals” added an optional parameter “skill” cosmetic
    • “jobs_skill_trends” added an optional parameter “location” cosmetic
    • “jobs_related_skills” reworded the description of “skill” cosmetic
    • “jobs_role_skills” reworded the description of “title” cosmetic
    • “jobs_salary_signals” reworded the description of “title” cosmetic
    • “jobs_skill_trends” reworded the description of “skill” cosmetic
    • “jobs_companies_hiring” dropped the optional parameter “role” cosmetic
    • “jobs_salary_signals” made “title” optional cosmetic
    • Tool “jobs_companies_hiring” changed its title: Jobs Companies Hiring → Top Hiring Companies cosmetic
    • Tool “jobs_related_skills” changed its title: Jobs Related Skills → Related Skills cosmetic
    • Tool “jobs_remote_trends” changed its title: Jobs Remote Trends → Remote-Work Trends cosmetic
    • Tool “jobs_role_skills” changed its title: Jobs Role Skills → Role Skills cosmetic
    • Tool “jobs_salary_signals” changed its title: Jobs Salary Signals → Salary Signals cosmetic
    • Tool “jobs_skill_trends” changed its title: Jobs Skill Trends → Job Skill Trends cosmetic
Diagnostics

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 29 Sept 2026 · Probed https://readyapis.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=readyapis.com CN=YE2,O=Let's Encrypt,C=US 8 Sept 2026 7 Dec 2026 ECDSA 256 ECDSA-SHA384 5113b28cc2c558922c82db09191fc5cd2b2
SANs: *.readyapis.com, readyapis.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of readyapis.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
readyapis.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=63072000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' https://www.googletagmanager.com https://static.cloudflareinsights.com https://challenges.cloudflare.com; frame-src https://challenges.cloudflare.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com; img-src 'self' data: https:; connect-src 'self' https://www.google-analytics.com https://analytics.google.com https://*.analytics.google.com https://www.googletagmanager.com https://cloudflareinsights.com; object-src 'none'; base-uri 'self'; frame-ancestors 'self'; form-action 'self' https://checkout.stripe.com https://billing.stripe.com; upgrade-insecure-requests
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://readyapis.com/mcp Verified 200
http (plaintext) http://readyapis.com/mcp HTTPS enforced 301 https://readyapis.com/mcp
MCP tools · 135 exposed · ~9,643 tokens

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 →

Tool Tokens
flight_reliability ~90

Return historical route reliability. Demo mode allows selected loaded routes such as ATL-LGA, ORD-EWR, SFO-SEA, LAX-JFK, DFW-LAX, and ATL-MCO.

NameTypeReqDescription
deststringyesDestination airport code, for example LGA.
monthinteger–Optional numeric month.
originstringyesOrigin airport code, for example ATL.

No output schema declared.

No examples provided.

flight_route_best_times ~43

Rank loaded departure-hour buckets for a route by historical reliability score.

NameTypeReqDescription
routestringyesRoute in ORIGIN-DEST format, for example ATL-LGA.

No output schema declared.

No examples provided.

flight_route_summary ~65

Return a combined historical route summary with reliability, cancellation risk, carriers, months, and best time bucket. This is not live tracking.

NameTypeReqDescription
deststringyesDestination airport code, for example LGA.
originstringyesOrigin airport code, for example ATL.

No output schema declared.

No examples provided.

fred_popular ~44

List of curated FRED series shortcuts with their underlying FRED ID, title, units, and frequency. Use this catalog to discover what slugs are available for fred_series.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

fred_search ~66

Free-text search of FRED's ~800k series catalog. Ordered by popularity. Use when you don't know the series ID — e.g. q='initial jobless claims' surfaces ICSA + state-level variants.

NameTypeReqDescription
limitinteger––
qstringyes–

No output schema declared.

No examples provided.

fred_series ~170

Fetch any FRED time-series by curated slug (gdp, cpi, unemployment, fed_funds, treasury_10y, vix, wti, mortgage_30y, ...) or raw FRED ID (CPIAUCSL, UNRATE, DGS10). ~800k series available — covers BLS, Census, Fed, Treasury, OECD, IMF, BIS. Free upstream, server-side key required.

NameTypeReqDescription
endstring–ISO date YYYY-MM-DD.
limitinteger––
series_or_slugstringyesCurated slug (e.g. 'gdp') or raw FRED series ID (e.g. 'CPIAUCSL').
sortstring––
startstring–ISO date YYYY-MM-DD.

No output schema declared.

No examples provided.

funding_signal ~150

SEC Form D-based funding-signal envelope. Pulls Form D / D-A filings live from EDGAR and surfaces a recency-weighted funding score, cadence hint (fresh_raise, recent_raise, established_cadence, stale), and buyer-shaped action_hint tuned by buyer profile (sales_outreach, vendor_partnerships, investor_research, recruiter). Form D filings are the public, free, authoritative record of private securities offerings.

NameTypeReqDescription
buyer_profilestring––
domainstring–Company domain. One of domain or ticker required.
limitinteger––
tickerstring–Stock ticker. Used when domain not provided.
window_daysinteger––

No output schema declared.

No examples provided.

fx_convert ~60

Convert an amount between two currencies at the most recent reference rate.

NameTypeReqDescription
amountnumberyes–
from_currencystringyesSource currency code, e.g. USD.
to_currencystringyesDestination currency code, e.g. EUR.

No output schema declared.

No examples provided.

fx_correlation ~63

Pearson correlation of daily log-returns vs USD across a basket. Cells banded strong_positive/positive/neutral/negative/strong_negative. Treasury/risk workflow for understanding multi-currency exposure.

NameTypeReqDescription
basketstring––
horizon_daysinteger––

No output schema declared.

No examples provided.

fx_currencies ~29

List every currency Ready APIs has reference-rate coverage for, with its issuing central bank and peg classification.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

fx_historical ~64

Reference rate for a specific past date. Useful for 'what was USD→EUR on 2024-11-15?' questions.

NameTypeReqDescription
basestring––
rate_datestringyesISO date, e.g. 2024-11-15.

No output schema declared.

No examples provided.

fx_movers ~63

Top N pairs by absolute % change over the lookback window. Returns signed pct_change + direction (up/down/flat). Daily/weekly market briefing.

NameTypeReqDescription
basketstring––
horizon_daysinteger––
top_ninteger––

No output schema declared.

No examples provided.

fx_pair ~69

Deep enrichment for one currency pair: latest rate + 30/90-day volatility + trend + anomaly z-score + spread estimate + cross-strength + verdict. Decision-grade single-call summary.

NameTypeReqDescription
basestringyesThree-letter base currency code.
quotestringyesThree-letter quote currency code.

No output schema declared.

No examples provided.

fx_rates ~39

Return current daily reference exchange rates relative to a base currency (default EUR), sourced from ECB.

NameTypeReqDescription
basestring–Three-letter base currency code.

No output schema declared.

No examples provided.

fx_strength ~64

Ranked strength leaderboard for the past N days. For each currency in the basket (g10 or majors), the average move across every pair it participates in. Strongest → weakest with per-currency label.

NameTypeReqDescription
basketstring––
horizon_daysinteger––

No output schema declared.

No examples provided.

fx_timeseries ~65

Daily rate series for a single base→quote pair across a date range. Useful for charts and trend analysis.

NameTypeReqDescription
basestringyes–
endstringyesISO end date.
quotestringyes–
startstringyesISO start date.

No output schema declared.

No examples provided.

fx_volatility_leaders ~76

Pairs ranked by annualized realized volatility. Distinct from fx_movers — surfaces pairs that swing wildly day-to-day, even if flat overall. Classes: low/moderate/elevated/extreme.

NameTypeReqDescription
basketstring––
horizon_daysinteger––
top_ninteger––

No output schema declared.

No examples provided.

geo_asn ~37

Resolve an IP to its autonomous system number, organization, and network prefix.

NameTypeReqDescription
ipstringyesIPv4 or IPv6 address.

No output schema declared.

No examples provided.

geo_city_search ~53

Return ZIP profiles for a city and state. Demo mode allows selected sample cities.

NameTypeReqDescription
namestringyesCity name, for example Atlanta.
statestringyesTwo-letter state code, for example GA.

No output schema declared.

No examples provided.

geo_county_lookup ~48

Return ZIP profiles in a county by county FIPS. Demo mode allows selected sample FIPS values.

NameTypeReqDescription
fipsstringyesCounty FIPS code, for example 13121.

No output schema declared.

No examples provided.

geo_enrich ~47

Return the enriched ZIP profile shape used by production enrichment workflows. Demo mode allows selected sample ZIPs.

NameTypeReqDescription
zipstringyesU.S. ZIP code, for example 30301.

No output schema declared.

No examples provided.

geo_ip ~68

Resolve an IPv4 or IPv6 address to city, state, country, coordinates, timezone, and the nearest US ZIP profile. Demo mode is limited to selected sample IPs.

NameTypeReqDescription
ipstringyesIPv4 or IPv6 address, for example 8.8.8.8.

No output schema declared.

No examples provided.

geo_nearby ~73

Return distance-sorted ZIP profiles near a coordinate. Demo mode allows selected sample coordinates, radius up to 25 miles, and limit up to 10.

NameTypeReqDescription
latnumberyesLatitude.
limitinteger––
lonnumberyesLongitude.
radius_milesnumber––

No output schema declared.

No examples provided.

geo_timezone ~40

Resolve a timezone using nearest ZIP centroid logic. Demo mode allows selected sample coordinates.

NameTypeReqDescription
latnumberyesLatitude.
lonnumberyesLongitude.

No output schema declared.

No examples provided.

geo_zip_batch ~69

Look up multiple ZIP profiles in one bounded request. Demo mode allows up to 5 selected sample ZIPs; production accepts up to 10.

NameTypeReqDescription
zip_codesarrayyesU.S. ZIP codes, for example ["30301", "10001"]. A comma-separated string is also accepted.

No output schema declared.

No examples provided.

geo_zip_lookup ~66

Look up a ZIP profile. Demo mode allows 30301, 30303, 10001, 94105, 60601, 78701, and 98101.

NameTypeReqDescription
zip_codestringyesU.S. ZIP code, for example 30301.

No output schema declared.

No examples provided.

hiring_signal ~172

Buyer-shaped hiring velocity envelope. Pass `domain`/`company` for a company-keyed view, or `location` (+ optional `role`) for a market-keyed view. Returns velocity score (0-100), tier, growth verdict (rapid_growth, active_growth, ...), and a sales_hint mapped to typical actions for the chosen buyer profile (saas_sales, recruiter, investor_diligence, competitive_intel).

NameTypeReqDescription
buyer_profilestring––
companystring–Company name (partial match).
domainstring–Company domain. One of domain/company/location required.
limitinteger––
locationstring–Location filter (city, metro, or 'remote').
rolestring–Role family filter (e.g. engineering, sales).

No output schema declared.

No examples provided.

intel_buyer_profiles ~30

List supported buyer profiles for /intel/company-signal and how each weights the six sub-scores.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

intel_change_profiles ~23

List buyer profiles for /intel/company-change and their category multipliers.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

intel_compliance_profiles ~26

List buyer profiles for /intel/compliance-signal and their sub-score weights.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

intel_cyber_profiles ~27

List buyer profiles for /intel/cyber-risk and their sub-score weights.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

intel_funding_profiles ~26

List buyer profiles for /intel/funding-signal and their sub-score weights.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

intel_hiring_profiles ~24

List buyer profiles for /intel/hiring-signal and their weights.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

intel_rank ~58

Score and rank up to 100 ZIPs against a single site profile. Returns sorted by risk_score (highest = lowest risk).

NameTypeReqDescription
candidatesarrayyesUp to 100 five-digit US ZIPs.
site_profilestring––

No output schema declared.

No examples provided.

intel_risk_profiles ~32

List supported risk profiles for /intel/counterparty-risk and how each weights the six risk sub-scores.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

intel_role_profiles ~51

List supported role profiles for /intel/location-score and how each weights the six sub-scores (talent_pool, cost_pressure, tax_burden, connectivity, climate_resilience, quality_of_life).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

intel_site_profiles ~30

List supported site profiles for /intel/site-risk and how each weights the six physical-risk sub-scores.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

jobs_companies_hiring ~50

Return curated company-level hiring signals for a location and optional role family.

NameTypeReqDescription
locationstringyesLocation query, for example atlanta.
rolestring–Optional role-family filter.

No output schema declared.

No examples provided.

jobs_companies_hiring ~59

Top companies hiring for a given skill or role. Returns company name + open-roles estimate + remote status + salary range when known.

NameTypeReqDescription
limitinteger––
skillstring––
titlestring––

No output schema declared.

No examples provided.

jobs_concentration ~69

HHI-based geographic concentration for a skill. Returns hhi_score (0-100), band (diffuse → dominant), and top N metros with their job-count share. Answers 'where does the candidate pool live?'.

NameTypeReqDescription
skillstringyes–
top_ninteger––

No output schema declared.

No examples provided.

jobs_momentum ~62

Recent vs prior period demand for a skill. Returns score (-100..+100) and band (surging/rising/stable/cooling/falling) so you know if hiring for this skill is accelerating or decelerating.

NameTypeReqDescription
skillstringyes–

No output schema declared.

No examples provided.

jobs_profile ~65

Full talent-market profile in one call: skill intel + role intel + market temperature + salary band + hiring velocity + location compete + talent verdict. Replaces ~5 separate calls.

NameTypeReqDescription
locationstring––
skillstring––
titlestring––

No output schema declared.

No examples provided.

jobs_related_skills ~33

Return ranked related skills for a loaded skill trend.

NameTypeReqDescription
skillstringyesSkill keyword, for example python.

No output schema declared.

No examples provided.

jobs_related_skills ~47

Top related skills frequently co-mentioned with a target skill. Useful for skill-graph traversal and job-description templating.

NameTypeReqDescription
limitinteger––
skillstringyes–

No output schema declared.

No examples provided.

jobs_remote_trends ~37

Return remote/hybrid/on-site trend buckets for a role title.

NameTypeReqDescription
rolestringyesRole title, for example software engineer.

No output schema declared.

No examples provided.

jobs_remote_trends ~43

Remote-work share by skill or title. Returns remote % alongside total job count and trend direction.

NameTypeReqDescription
skillstring––
titlestring––

No output schema declared.

No examples provided.

jobs_role_skills ~41

Return aggregated skill signals for a role title. Demo mode allows selected sample job titles.

NameTypeReqDescription
titlestringyesRole title, for example data analyst.

No output schema declared.

No examples provided.

jobs_role_skills ~45

Skills most commonly required for a given job title (e.g. 'staff engineer', 'product manager').

NameTypeReqDescription
limitinteger––
titlestringyes–

No output schema declared.

No examples provided.

jobs_salary_signals ~38

Return salary signal aggregates for a role title in the loaded trend set.

NameTypeReqDescription
titlestringyesRole title, for example cloud engineer.

No output schema declared.

No examples provided.

jobs_salary_signals ~58

Salary range + midpoint + band tier (junior/mid/senior/staff) for a skill or title. Useful for comp benchmarking and job-posting copy.

NameTypeReqDescription
skillstring––
titlestring––

No output schema declared.

No examples provided.

Common questions

What is the Ready APIs MCP server?

Ready APIs is an MCP server listed in the public MCP registry as com.readyapis/api. 135 MCP tools: geo, email, phone, company, DNS, FX, equities, weather, tax, econ, intel, one key. This page covers its hosted endpoint (https://readyapis.com/mcp).

Is the Ready APIs MCP server safe to use?

Ready APIs scores 86 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 Ready APIs MCP server expose?

Ready APIs exposes 135 tools: meta_catalog, meta_dataset, geo_zip_lookup, geo_zip_batch, geo_enrich, and 130 more. Their descriptions and schemas cost roughly 9,643 tokens of context every time the server is loaded.

Does the Ready APIs MCP server require authentication?

No. We connected to Ready APIs without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Ready APIs MCP server still maintained?

Ready APIs is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.