Is com.readyapis/api up? Live MCP status

Not checked just now. The live check did not run for this request (more than 120 status pages asked for a fresh check in the last minute). Reload in a minute; the monthly census result is below.

Endpointhttps://readyapis.com/mcp
Page built

One MCP handshake with the listed endpoint (server/discover at 2026-07-28, then initialize for a server on the older revision), with no credential and no retry, identifying itself as agentwares-mcp-liveness/0.1 (+https://agentwares-agentcheck.vercel.app/bot). It runs when this page is requested and the result is reused for 10 minutes, so the time above is when it was taken.

Live status every few hours: Wellknown

Email me when this server changes

That was one look. To hear when it stops answering or its tools change, leave an address.

Free, no password or GitHub: one confirmation email first, then a check every hour and an email when it stops answering or its tools change. Every email has a link to stop. More about it.

Monthly census, 6 October 2026

The census sends the same request to every remote listing in the official registry once a month. On 6 October 2026 this one answered a stock client with no credential. Every listing’s result: index.ndjson (what the files hold: index.meta.json).

Agent discovery documents at this origin

A2A agent cardNot published (HTTP 404).
/.well-known/agent-card.json
MCP server card (SEP-2127)Not published (HTTP 404).
https://readyapis.com/mcp/server-card
MCP server card (SEP-1649 location)Not published (HTTP 404).
/.well-known/mcp/server-card.json — SEP-1649, a draft superseded by SEP-2127 on 21 January 2026
Web Bot Auth key directoryNot published (HTTP 404).
/.well-known/http-message-signatures-directory

Read at https://readyapis.com with the monthly census on 9 October 2026: one GET each, no credential, never a signed request. A2A against v1.0.1, the server card against the MCP Server Card schema (SEP-2127), the card at SEP-1649’s location against the shape it has, the key directory against the Web Bot Auth draft of 1 September 2026. Who publishes them.

Tool changes between snapshots

In the 2026-10 snapshot it listed 135 tools: address_enrich, address_validate, address_validate_batch, bin_lookup, calendar_business_days_add, calendar_holidays, calendar_is_business_day, company_change, company_changes, company_cik, company_classify, company_domain, company_domains_batch, company_enrich, company_industry, company_insights, company_lookup_auto, company_lookup_batch, company_network, company_nonprofit_ein, company_nonprofit_search, company_peer_comparison, company_registration, company_search, company_signal, company_stats, company_ticker, company_timeline, compliance_signal, counterparty_risk, cyber_risk, dns_certificates, dns_compare, dns_history, dns_lookup, dns_profile, dns_reputation, dns_tls, dns_whois, email_disposable, email_free_provider, email_smtp_probe, email_validate, equities_concept, equities_filings, equities_fundamentals, equities_ticker, flight_airline_reliability, flight_airport_delay_profile, flight_cancellation_risk, flight_reliability, flight_route_best_times, flight_route_summary, fred_popular, fred_search, fred_series, funding_signal, fx_convert, fx_correlation, fx_currencies, fx_historical, fx_movers, fx_pair, fx_rates, fx_strength, fx_timeseries, fx_volatility_leaders, geo_asn, geo_city_search, geo_county_lookup, geo_enrich, geo_ip, geo_nearby, geo_timezone, geo_zip_batch, geo_zip_lookup, hiring_signal, intel_buyer_profiles, intel_change_profiles, intel_compliance_profiles, intel_cyber_profiles, intel_funding_profiles, intel_hiring_profiles, intel_rank, intel_risk_profiles, intel_role_profiles, intel_site_profiles, jobs_companies_hiring, jobs_companies_hiring, jobs_concentration, jobs_momentum, jobs_profile, jobs_related_skills, jobs_related_skills, jobs_remote_trends, jobs_remote_trends, jobs_role_skills, jobs_role_skills, jobs_salary_signals, jobs_salary_signals and 35 more.

No change to its tools between 2026-09 and 2026-10.

Which tools were added or removed, and whose description or schemas changed, from content hashes in the monthly snapshots. Per tool, as JSON: /v1/drift.

The listing

Registry namecom.readyapis/api
Endpointhttps://readyapis.com/mcp
Publisher repositorynot known: the registry did not return this listing within 4 seconds

Also

The full check by name, as JSON (on a 401 it also follows the OAuth discovery chain) · Watch it · Check another server · llms.txt

Free, no key, no signup. Terms · Privacy