PtData
REMOTE · API.PTDATA.IO
Point-in-time US equity fundamentals for quants and AI agents. Free tier, no API key needed.
Available components
Last scanned (23 hours ago)
Scores higher than 55% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Finance and Payments
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 524 tokens (~131/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 0
- Tool “get_earnings_event” rewrote its description, which is the text the model reads security
- Tool “get_fundamentals” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 29 Oct 26 67
First indexed and scored.
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 4 Nov 2026 · Probed https://api.ptdata.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.ptdata.io | CN=YE2,O=Let's Encrypt,C=US | 12 Sept 2026 | 11 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 56d390102768496ed13f01f9cc058c4e45b |
| SANs: api.ptdata.io | ||||||
| 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 api.ptdata.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| ptdata.io. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.ptdata.io/mcp | Verified | 200 | |
| http (plaintext) | http://api.ptdata.io/mcp | HTTPS enforced | 308 | https://api.ptdata.io/mcp |
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 →
get_earnings_event Get earnings event ~72
Earnings event: 8-K acceptance timestamp, and as-reported revenue and eps_gaap from the original report. `fiscal_period` is FY or Q1..Q4.
| Name | Type | Req | Description |
|---|---|---|---|
| fiscal_period | string | yes | – |
| fiscal_year | integer | yes | – |
| ticker | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_filing_metadata Get filing metadata ~52
SEC filings for `ticker` available on `as_of_date`, newest first, with amendment linkage.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of_date | string | yes | – |
| form_type | – | – | – |
| ticker | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_fundamentals Get point-in-time fundamentals ~227
Point-in-time fundamentals for `ticker` as known on `as_of_date` (YYYY-MM-DD). Returns each available metric's value for the fiscal period with source + knowledge time + lineage under `metrics`. Any requested metric with no value appears under `unavailable` with `{reason, code, available_alternatives, docs_url}` instead of being silently dropped. `code` is `not_reported` or `financials_family`. `revenue` keeps the headline tag first filed for that period (including `RevenuesNetOfInterestExpense` for brokers and card issuers) and follows that tag's own restatements. A later tag does not replace it, and components are not summed. A financial with only component lines gets `financials_family` and the populated members. Check `unavailable` before concluding a figure does not exist.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of_date | string | yes | – |
| fiscal_period | string | – | – |
| fiscal_year | – | – | – |
| metrics | array | yes | – |
| ticker | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_index_constituents Get index constituents ~62
S&P 500 (or other index) constituents as understood on `as_of_date` (YYYY-MM-DD), survivorship-free. Point-in-time, with lineage.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of_date | string | yes | – |
| index | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the PtData MCP server?
PtData is a hosted endpoint at https://api.ptdata.io/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 · api.ptdata.io
claude mcp add --transport http io-ptdata-ptdata 'https://api.ptdata.io/mcp'
What is the PtData MCP server?
PtData is an MCP server listed in the public MCP registry as io.ptdata/ptdata. Point-in-time US equity fundamentals for quants and AI agents. Free tier, no API key needed. This page covers its hosted endpoint (https://api.ptdata.io/mcp).
Is the PtData MCP server safe to use?
PtData scores 70 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 PtData MCP server expose?
PtData exposes 4 tools: get_index_constituents, get_fundamentals, get_filing_metadata, get_earnings_event. Their descriptions and schemas cost roughly 413 tokens of context every time the server is loaded.
Does the PtData MCP server require authentication?
No. We connected to PtData without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the PtData MCP server still maintained?
PtData is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.