Home / MCP registry index / com.mcpscores/public-data-api

MCPFax Public-Data Utility API

com.mcpscores/public-data-api in the official MCP registry. Endpoint https://mcpfax-utility.bowling-anthony.workers.dev/mcp.

The registry describes it as: One public fact when you have no API key: where, what time, what rate. 31 lookups.

We read its 31 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Tools it advertises

v1_geocode v1_reverse_geocode v1_timezone v1_zip v1_airports_nearest v1_ip_geolocation v1_country v1_weather v1_weather_alerts v1_air_quality v1_sun v1_holidays v1_business_days v1_fx v1_crypto_price v1_stock_quote v1_sec_company_facts v1_inflation v1_econ_indicator v1_lei v1_vin_decode v1_icd10 v1_naics v1_cfr v1_drug_label v1_wikipedia v1_unit_convert v1_dns v1_rdap v1_robots v1_validate_email

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/com-mcpscores-public-data-api/badge.svg)](https://lazaretto.dev/mcp-registry/com-mcpscores-public-data-api)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.