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

remote · readyapis.com 86
+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
address_enrich ~55

Validate a US address and return the full ZIP enrichment (demographics, risk, climate, nearest airport, hazards) in one call.

NameTypeReqDescription
addressstringyesFree-form US address: street, city, state, ZIP.

No output schema declared.

No examples provided.

address_validate ~60

Parse and validate a free-form US address: standardize street/unit/city/state/ZIP and cross-check the ZIP against the geo dataset for state and city consistency.

NameTypeReqDescription
addressstringyesFree-form US address — street, city, state, ZIP.

No output schema declared.

No examples provided.

address_validate_batch ~42

Validate up to 50 US addresses in one request. Per-item errors are returned inline.

NameTypeReqDescription
itemsarrayyesUp to 50 free-form US addresses.

No output schema declared.

No examples provided.

bin_lookup ~133

Identify the issuing bank, scheme (Visa / Mastercard / Amex / etc), card type (credit/debit/prepaid), and country behind a card BIN. Accepts a 6-8 digit BIN or a full PAN (Luhn-checked, never echoed). Returns scheme + card_type + brand + issuer_bank + country + risk_band. PCI-safe.

NameTypeReqDescription
card_or_binstringyes6-8 digit BIN or full PAN (with or without spaces/dashes).
use_binlist_fallbackboolean–When false, force offline-only response (curated table + scheme prefix detection only).

No output schema declared.

No examples provided.

calendar_business_days_add ~43

Add N business days to a date and return the resulting business day.

NameTypeReqDescription
datestringyesStart date YYYY-MM-DD.
daysintegeryes–

No output schema declared.

No examples provided.

calendar_holidays ~32

List US federal holidays for a year, including observed dates per OPM rules.

NameTypeReqDescription
yearinteger––

No output schema declared.

No examples provided.

calendar_is_business_day ~39

Check whether a US date is a business day (weekday and not a federal holiday).

NameTypeReqDescription
datestringyesISO date YYYY-MM-DD.

No output schema declared.

No examples provided.

company_change ~152

SEC 8-K change-signal envelope for a public company. Pulls recent 8-K filings live from EDGAR, classifies item codes into change categories (M&A, leadership, restructuring, material agreement, financial, auditor, governance, disclosure), and returns a change-velocity score (0-100), dominant theme, and buyer-shaped action_hint tuned by buyer profile (sales_outreach, recruiter, investor_research, competitive_intel).

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.

company_changes ~151

Vendor / counterparty change monitoring. Returns time-ordered entity changes (status flips, parent acquisitions, renames) filtered by since-date, LEI, change_type, or country. Critical for continuous KYC and M&A monitoring.

NameTypeReqDescription
change_typestring–Filter by change type. Comma-separated for multiple.
countrystring–ISO 3166-1 alpha-2 country.
domainstring–Restrict via domain resolution.
leistring–Restrict to a single LEI.
pagestring––
per_pagestring––
sincestring–ISO 8601 datetime or date. Default 7 days ago.

No output schema declared.

No examples provided.

company_cik ~74

Resolve a SEC EDGAR Central Index Key (CIK) to a unified company profile. Accepts CIK with or without leading zeros (320193 = 0000320193 = Apple).

NameTypeReqDescription
cikstringyesSEC EDGAR CIK, e.g. '320193' or '0000320193'.

No output schema declared.

No examples provided.

company_classify ~37

Classify a domain using the loaded curated company profile set.

NameTypeReqDescription
urlstringyesDomain or URL, for example nvidia.com.

No output schema declared.

No examples provided.

company_domain ~33

Return a company profile by domain. Demo mode allows selected sample domains.

NameTypeReqDescription
domainstringyesCompany domain or URL.

No output schema declared.

No examples provided.

company_domains_batch ~55

Return multiple company profiles by domain in one bounded request. Demo mode allows selected sample domains.

NameTypeReqDescription
domainsarrayyesCompany domains, for example ["apple.com", "microsoft.com"]. A comma-separated string is also accepted.

No output schema declared.

No examples provided.

company_enrich ~47

One-call company enrichment: identity + DNS + tech stack + SEC filings (if public) + cyber risk score.

NameTypeReqDescription
domainstringyesCompany domain, e.g. stripe.com.

No output schema declared.

No examples provided.

company_industry ~36

Search loaded curated company profiles by industry, category, or description signals.

NameTypeReqDescription
industrystringyesIndustry query, for example technology.

No output schema declared.

No examples provided.

company_insights ~139

Single-call mega-endpoint — subject profile + hierarchy + corporate-family network + lifecycle timeline + peer benchmark in one response. The 'everything we know' company call.

NameTypeReqDescription
domainstring––
include_changesboolean––
include_filingsboolean–Live SEC EDGAR filings fetch (adds latency; public companies only).
include_hierarchyboolean––
include_networkboolean––
include_peersboolean––
include_risk_indicatorsboolean––
include_timelineboolean––
leistring––
tickerstring––

No output schema declared.

No examples provided.

company_lookup_auto ~91

Auto-detect identifier type and route. Accepts LEI, CIK, domain, email, ticker, or exact name. Returns resolution.matched_on so caller can confirm what type was used.

NameTypeReqDescription
identifierstringyesAny of: LEI (20 chars), CIK (digits), domain (has dot), email (has @), ticker (1-5 letters), or exact company name.

No output schema declared.

No examples provided.

company_lookup_batch ~48

Resolve up to 50 mixed identifiers (domain, LEI, ticker, name) in a single POST. Each result preserves the original input for join-back.

NameTypeReqDescription
identifiersarrayyes–

No output schema declared.

No examples provided.

company_network ~94

Walk the GLEIF ultimate-parent hierarchy and return every entity sharing the same conglomerate root. Excludes pension/retirement trusts by default.

NameTypeReqDescription
domainstring–Resolve subject by domain.
include_pension_trustsboolean––
leistring–Resolve subject by GLEIF LEI.
pageinteger––
per_pageinteger–1-200.

No output schema declared.

No examples provided.

company_nonprofit_ein ~38

Return a nonprofit identity profile by EIN.

NameTypeReqDescription
einstringyesEmployer Identification Number, for example 20-0049703.

No output schema declared.

No examples provided.

company_nonprofit_search ~49

Search nonprofit identity profiles by name, category, EIN, or state.

NameTypeReqDescription
qstringyesSearch query, for example education.
statestring–Optional two-letter state filter.

No output schema declared.

No examples provided.

company_peer_comparison ~87

Benchmark a company against same-industry/same-country peers — employee distribution, jurisdiction mix, founding-decade histogram, and where the subject ranks within the peer set.

NameTypeReqDescription
domainstring–Resolve subject by domain.
leistring–Resolve subject by GLEIF LEI.
scopestring––
tickerstring–Resolve subject by ticker.

No output schema declared.

No examples provided.

company_registration ~114

Resolve a registry-assigned registration number (Companies House, Delaware file number, Handelsregisternummer, etc.) to a company profile. Pass country= to disambiguate since regnums aren't globally unique.

NameTypeReqDescription
countrystring–Optional ISO 3166-1 alpha-2 country code to disambiguate.
jurisdictionstring–Optional ISO 3166-2 jurisdiction for finer scoping.
regnumstringyesRegistration number, e.g. Stripe's Delaware file number '4675506'.

No output schema declared.

No examples provided.

company_search ~43

Search loaded curated company profiles by name, domain, industry, or ticker. Demo mode allows selected sample queries.

NameTypeReqDescription
qstringyesSearch query, for example technology.

No output schema declared.

No examples provided.

company_signal ~178

Composite B2B buyer-signal score (0-100) for a company. Joins curated identity + live SEC EDGAR filings + DNS/DMARC + WHOIS + curated hiring signals into one explainable score tuned by buyer profile (enterprise_sales, smb_sales, investor_research, vendor_diligence). Returns overall score, tier, verdict, six sub-scores with notes, tech-stack hint, and SEC activity summary.

NameTypeReqDescription
buyer_profilestring–Buyer profile that tunes the sub-score weights.
domainstring–Company domain (e.g. apple.com). One of domain or ticker is required.
include_filingsboolean–Fetch live SEC EDGAR filings (adds ~400ms upstream).
tickerstring–Stock ticker (e.g. AAPL). Used when domain is not provided.

No output schema declared.

No examples provided.

company_stats ~143

Return aggregate counts across the 3.3M-entity registry — by country, jurisdiction, industry, entity_type, employee_range, decade founded, plus hierarchy/data-quality coverage. Filter the slice with country/jurisdiction/industry/naics.

NameTypeReqDescription
countrystring–ISO 3166-1 alpha-2 country, e.g. 'US'.
industrystring–Industry keyword.
jurisdictionstring–ISO 3166-2 jurisdiction, e.g. 'US-DE'.
naics_codestring–2-digit NAICS sector code.
top_ninteger–Items returned per facet (1-50).

No output schema declared.

No examples provided.

company_ticker ~34

Return a loaded curated company profile by public ticker.

NameTypeReqDescription
tickerstringyesTicker symbol, for example NVDA.

No output schema declared.

No examples provided.

company_timeline ~71

Chronological lifecycle event list for any company — founding year, SEC former-name rebrand events, current status, parent disclosures.

NameTypeReqDescription
domainstring–Resolve subject by domain.
leistring–Resolve subject by GLEIF LEI.
tickerstring–Resolve subject by ticker.

No output schema declared.

No examples provided.

compliance_signal ~160

Compliance-status snapshot for a company: screens against Treasury OFAC SDN entries and SEC enforcement actions, and returns a 0-100 compliance score, tier, decision_hint (proceed / proceed_with_review / escalate / block_pending_review), and critical flags. Tuned by buyer profile (kyc_onboarding, vendor_diligence, regulated_industry, marketplace_listing). SCOPE: decision-support only — does not replace formal KYC or licensed sanctions screening.

NameTypeReqDescription
buyer_profilestring––
companystring–Company name. One of company / domain / ticker required.
domainstring–Company domain — used to resolve canonical name.
tickerstring–Stock ticker — used to resolve canonical name + CIK.

No output schema declared.

No examples provided.

counterparty_risk ~151

B2B counterparty-risk composite: should we extend terms to this company? Joins curated identity + live SEC EDGAR filings + DNS/DMARC + WHOIS into a risk-weighted 0-100 score (higher = lower risk), plus a tier and a decision_hint that maps to AR/AP actions (approve_net_30, approve_with_credit_check, require_prepayment, decline_pending_review). Supports four risk profiles for different underwriting postures.

NameTypeReqDescription
domainstring–Company domain. One of domain or ticker required.
include_filingsboolean––
risk_profilestring––
tickerstring–Stock ticker. Used when domain not provided.

No output schema declared.

No examples provided.

cyber_risk ~122

DNS-hygiene + tech-stack-exposure surface for a domain. Returns a 0-100 cyber score (higher = lower risk) with six sub-scores (email security, DNS hardening, domain hygiene, infra exposure, tech-stack exposure, spoofability), critical flags, and concrete recommended actions. Tuned by buyer profile. SCOPE: inspects published DNS only — no port scans, breach lookups, or CVE matching.

NameTypeReqDescription
buyer_profilestring––
domainstringyesCompany domain, e.g. example.com.

No output schema declared.

No examples provided.

dns_certificates ~75

Recent SSL certificates from Certificate Transparency logs (crt.sh). Returns recent certs with issuer + expiry, plus the deduped subdomain list discovered across all CT entries. Useful for shadow-IT detection, sales-intel hostname discovery, and phishing-cert monitoring.

NameTypeReqDescription
domainstringyes–
limitinteger––

No output schema declared.

No examples provided.

dns_compare ~120

Compare a target domain against a reference for phishing / typosquatting / lookalike detection. Computes edit distance, apex/TLD diff, homoglyph substitution detection (0↔o, 1↔l, rn↔m). Flags is_likely_typosquat + is_likely_lookalike with drivers. Pure analytical comparison — no DNS query.

NameTypeReqDescription
referencestringyesKnown-good domain, e.g. stripe.com.
targetstringyesSuspect domain, e.g. striipe.com.

No output schema declared.

No examples provided.

dns_history ~123

Snapshot-on-query passive-DNS view. Returns every (record_type, value) tuple seen for this domain during /dns/lookup calls, with first_seen + last_seen + observation_count. Useful for detecting when A records moved or recovering historical NS/MX values. Not a global feed — accumulates from when our users first resolve a domain.

NameTypeReqDescription
domainstringyes–
limit_per_typeinteger––
record_typestring–Optional filter: A / AAAA / MX / TXT / NS / CNAME / SOA / CAA.

No output schema declared.

No examples provided.

dns_lookup ~61

Resolve A, AAAA, MX, TXT, NS, CNAME, SOA, and CAA records for a domain.

NameTypeReqDescription
domainstringyesDomain name, e.g. example.com.
typesstring–Optional comma-separated record types.

No output schema declared.

No examples provided.

dns_profile ~70

Complete DNS + WHOIS + security + hosting + email-infrastructure + subdomain-probe + health-verdict picture in one call. Sales-intel and security-audit workflow.

NameTypeReqDescription
domainstringyes–
skip_subdomainsboolean––
skip_whoisboolean––

No output schema declared.

No examples provided.

dns_reputation ~67

Composite 0-100 reputation score combining domain age, registrar tier, expiration window, security grade, NS diversity, and hosting tier. Returns band (high/moderate/low/suspect) + contributing factors. Designed for fraud-screening pipelines.

NameTypeReqDescription
domainstringyes–

No output schema declared.

No examples provided.

dns_tls ~73

Open a TLS handshake on :443, capture the presented cert + protocol version + cipher, and grade the result A-F. Surfaces days-until-expiry, SAN list, self-signed detection, and findings like 'CBC-mode cipher in use'.

NameTypeReqDescription
domainstringyes–
portinteger––

No output schema declared.

No examples provided.

dns_whois ~44

Public WHOIS profile: registrar, creation date, expiration, name servers, age in years.

NameTypeReqDescription
domainstringyesDomain name, e.g. example.com.

No output schema declared.

No examples provided.

email_disposable ~39

Test whether a domain belongs to the curated disposable-email-domain list.

NameTypeReqDescription
domainstringyesDomain to test, e.g. mailinator.com.

No output schema declared.

No examples provided.

email_free_provider ~39

Test whether a domain belongs to the curated free consumer-email-provider list.

NameTypeReqDescription
domainstringyesDomain to test, e.g. gmail.com.

No output schema declared.

No examples provided.

email_smtp_probe ~110

Live SMTP RCPT probe (HELO + MAIL FROM + RCPT TO; no DATA). Reports deliverability verdict (deliverable / catch_all / undeliverable / greylisted / inconclusive). Catch-all detection via random-fake-RCPT comparison. Skipped automatically for Gmail / Outlook / Yahoo / iCloud / Fastmail / ProtonMail. ~3-8s latency.

NameTypeReqDescription
check_catch_allboolean––
emailstringyesEmail address to probe.

No output schema declared.

No examples provided.

email_validate ~65

Validate an email address: RFC syntax, MX lookup, disposable/free/role-account flags, typo correction, and a composite deliverability score. Demo mode is allowed; no live SMTP probe.

NameTypeReqDescription
check_dnsboolean––
emailstringyesEmail address to validate.

No output schema declared.

No examples provided.

equities_concept ~86

Full observation history for one XBRL concept (any us-gaap tag). Use for fields outside our 35-item headline catalog. Returns every observation across every reported unit, most-recent first.

NameTypeReqDescription
conceptstringyesus-gaap XBRL tag, e.g. ResearchAndDevelopmentExpense.
include_segmentsboolean––
tickerstringyes–

No output schema declared.

No examples provided.

equities_filings ~106

Live SEC EDGAR submissions API: most recent filings (10-K, 10-Q, 8-K, ...) for a ticker or CIK. Filter by form type.

NameTypeReqDescription
cikstring–SEC CIK. Either ticker or cik is required.
formsstring–Optional comma-separated form types, e.g. '10-K,10-Q'.
limitinteger––
tickerstring–Stock ticker. Either ticker or cik is required.

No output schema declared.

No examples provided.

equities_fundamentals ~91

Headline financial statements parsed from SEC XBRL filings: revenue, net income, total assets, EPS, cash flow, and 30 more curated tags. Annual (10-K) or quarterly (10-Q). Free — backed by SEC's public XBRL companyfacts API.

NameTypeReqDescription
limitinteger––
periodstring––
tickerstringyesStock ticker.

No output schema declared.

No examples provided.

equities_ticker ~50

Resolve a stock ticker to company name, CIK, exchange, SIC industry code, and headquarters from the SEC EDGAR registry.

NameTypeReqDescription
tickerstringyesStock ticker, e.g. AAPL.

No output schema declared.

No examples provided.

flight_airline_reliability ~38

Summarize loaded route reliability signals for a carrier code.

NameTypeReqDescription
airline_codestringyesCarrier code, for example DL.

No output schema declared.

No examples provided.

flight_airport_delay_profile ~41

Summarize delay and reliability signals for an airport across loaded loaded route aggregates.

NameTypeReqDescription
airport_codestringyesAirport code, for example ATL.

No output schema declared.

No examples provided.

flight_cancellation_risk ~65

Return historical cancellation-risk signals for a route. This is not live tracking.

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

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.