Fmp
REMOTE · GATEWAY.PIPEWORX.IO · SCANNED AUG 3
Financial Modeling Prep MCP (/stable API; v3 deprecated 2025-08-31).
Available components
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 →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: this server exposes a tool marked destructive (forget) and its handshake is open, but we could not confirm whether a tool call is gated, so we do not assert it is callable unauthenticated. View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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 Usability63
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (fair).Partial
- Context-footprint check failed: tool/resource definitions use about 11208 tokens (~203/item across 55 items; 55 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Tools include usage examples.Pass
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 69% of tool parameters carry a description.Partial
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · gateway.pipeworx.io
claude mcp add --transport http pipeworx-io-fmp https://gateway.pipeworx.io/fmp/mcp
[mcp_servers.pipeworx-io-fmp] url = "https://gateway.pipeworx.io/fmp/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"pipeworx-io-fmp": {
"type": "remote",
"url": "https://gateway.pipeworx.io/fmp/mcp",
"enabled": true
}
}
} openclaw mcp add pipeworx-io-fmp --url https://gateway.pipeworx.io/fmp/mcp --transport streamable-http
mcp_servers:
pipeworx-io-fmp:
url: "https://gateway.pipeworx.io/fmp/mcp" {
"mcpServers": {
"pipeworx-io-fmp": {
"type": "http",
"url": "https://gateway.pipeworx.io/fmp/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 3 Aug 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “deep_research” rewrote its description, which is the text the model reads security
- Tool “ask_pipeworx” rewrote its description, which is the text the model reads security
- Tool “ask_pipeworx_grounded” rewrote its description, which is the text the model reads security
- Tool “ask_pipeworx_beta” rewrote its description, which is the text the model reads security
- 2 Aug 26 −2
No change was recorded against any check on this day. Schema Quality & AI Usability went from 72 to 63. Other categories moved too: Stability & Change Management rose 3, Tool Coverage rose 2.
- 1 Aug 26 +1
- Authorization: fail → unverified ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “ask_pipeworx” rewrote its description, which is the text the model reads security
- Tool “deep_research” rewrote its description, which is the text the model reads security
- Tool “ask_pipeworx_grounded” rewrote its description, which is the text the model reads security
- Tool “ask_pipeworx_beta” rewrote its description, which is the text the model reads security
- 31 Jul 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
- 30 Jul 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
- 29 Jul 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “ask_pipeworx” rewrote its description, which is the text the model reads security
- Tool “deep_research” rewrote its description, which is the text the model reads security
- Tool “ask_pipeworx_grounded” rewrote its description, which is the text the model reads security
- Tool “ask_pipeworx_beta” rewrote its description, which is the text the model reads security
- 28 Jul 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “ask_pipeworx_beta” rewrote its description, which is the text the model reads security
- Tool “deep_research” rewrote its description, which is the text the model reads security
- Tool “ask_pipeworx_grounded” rewrote its description, which is the text the model reads security
- Tool “ask_pipeworx” rewrote its description, which is the text the model reads security
- 27 Jul 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
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 3 Aug 2026 · Probed https://gateway.pipeworx.io/fmp/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pipeworx.io | CN=WE1,O=Google Trust Services,C=US | 20 Jul 2026 | 18 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 8b854960bb5cdb890e68540cbf9f08a8 |
| SANs: pipeworx.io, gateway.pipeworx.io, *.gateway.pipeworx.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of gateway.pipeworx.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| pipeworx.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 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://gateway.pipeworx.io/fmp/mcp | Verified | 200 | |
| http (plaintext) | http://gateway.pipeworx.io/fmp/mcp | Served over HTTP | 200 |
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.
stock_screener Stock Screener ~293
Stock screener (paid).
| Name | Type | Req | Description |
|---|---|---|---|
| betaLowerThan | number | — | Maximum beta. |
| betaMoreThan | number | — | Minimum beta. |
| country | string | — | 2-letter country code, e.g. "US". |
| dividendLowerThan | number | — | Maximum dividend yield. |
| dividendMoreThan | number | — | Minimum dividend yield. |
| exchange | string | — | e.g. "NASDAQ", "NYSE". |
| industry | string | — | e.g. "Semiconductors", "Biotechnology". |
| isActivelyTrading | string | — | "true" | "false" |
| isEtf | string | — | "true" | "false" |
| limit | number | — | Max rows (default 100). At least one filter should be set, or this is a slice of the whole exchange rather than a screen. |
| marketCapLowerThan | number | — | Maximum market cap in USD. |
| marketCapMoreThan | number | — | Minimum market cap in USD, e.g. 1000000000 for $1B+. |
| priceLowerThan | number | — | Maximum share price. |
| priceMoreThan | number | — | Minimum share price. |
| sector | string | — | e.g. "Technology", "Healthcare", "Energy", "Financial Services". |
| volumeLowerThan | number | — | Maximum average volume. |
| volumeMoreThan | number | — | Minimum average volume. |
No output schema declared.
No examples provided.
subscribe Subscribe to Alerts ~449
Create a proactive monitoring subscription to a live-data event stream. Returns the new subscription id. Requires a Pipeworx OAuth account (anonymous + BYO cannot persist subscriptions). Supported types: "sec_8k" (8-K filings matching ticker + item codes — e.g. items:["5.02"] = officer change), "polymarket_edge" (Polymarket↔Kalshi cross-venue mispricings — params:{topic:"fed"}), "fred_series" (new FRED observations — params:{series_id:"UNRATE"}). Delivery channels: feed (always on — pull via recent_alerts or GET registry.pipeworx.io/alerts.json), and optionally email (set delivery:{email:"[email protected]"}) or sms (delivery:{sms:"+15551234567"} — phone must be verified at /account first; 10/day cap).
| Name | Type | Req | Description |
|---|---|---|---|
| delivery | object | — | Optional delivery channels in addition to the always-on persistent feed. {email:"[email protected]"} sends a templated alert per fired event. {sms:"+15551234567"} sends an SMS per event — must match the veri… |
| params | object | yes | Type-specific filter. sec_8k: {ticker:"AAPL", items?:["5.02","1.01"]}. polymarket_edge: {topic:"fed", min_spread_bps?:500}. fred_series: {series_id:"UNRATE"}. patent_grant: {applicant:"Apple Inc."}.… |
| type | string | yes | Subscription type. |
No output schema declared.
No examples provided.
suggest_questions What Can I Ask Pipeworx? ~240
What can I ask Pipeworx? / what is Pipeworx good for? / what can you do? / give me ideas / show me examples / getting started / what data do you have? — the onboarding entry point for an agent that just connected and wants to know what is worth asking. Returns category-bucketed example questions (company financials, drugs & clinical trials, economics, real estate, prediction markets, weather, government & patents, science & academia, news) — each with the exact tool + argument shape that answers it, drawn from the live catalog of thousands of tools. Call with no arguments for the full spread, or pass `topic` (e.g. "finance", "pharma", "betting") to focus. Use this FIRST when you do not yet know what Pipeworx can do for you, or to learn how to call the meta-tools (ask_pipeworx, entity_profile, compare_entities, etc.).
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | — | Optional focus area: finance | pharma | economics | real-estate | betting | weather | government | science | news. Omit for a cross-category spread. |
No output schema declared.
No examples provided.
unsubscribe Unsubscribe from Alerts ~60
Cancel a subscription by id. Ownership is enforced — you can only cancel your own subscriptions. The row is deactivated (not deleted) so its historical events stay available via recent_alerts.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Subscription id (uuid) returned by subscribe. |
No output schema declared.
No examples provided.
validate_claim Validate Claim ~306
"Is it true that…" / "fact check" / "verify the claim that…" / "did X really…" / "was Y actually…" / "confirm or refute" / "true or false" — natural-language claim verification against authoritative sources. Use whenever the agent needs to check whether something a user said is factually correct. Company-financial claims (revenue, net income, cash for public US companies) verify via the structured SEC EDGAR + XBRL fast path with exact percent-delta math; ANY OTHER factual claim (macro statistics, rates, prices, drug data, records) automatically falls through to the grounded pipeline — routed to the right live source, answered with verbatim evidence, then judged. Returns a verdict (confirmed / approximately_correct / refuted / inconclusive / unsupported), the grounded or structured actual value with pipeworx:// citation, and reasoning. Replaces 4–6 sequential calls (NL parsing → entity resolution → data lookup → comparison).
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | yes | Natural-language factual claim, e.g., "Apple's FY2024 revenue was $400 billion" or "Microsoft made about $100B in profit last year". |
| tolerance_pct | number | — | Max percent deviation still graded approximately_correct (0.5–50). Overrides the tolerance implied by the claim wording — set 1–2 for hallucination detection where any material error must be refuted.… |
No output schema declared.
No examples provided.