Polymarket and Predict.fun historical tick data, plus backtest quotes and status, over MCP
Nothing to run from here
Fd Daas is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
93/100
trust score
50
tools declared
local
runs on your machine
—
calls last 7d
What it does
Consolidated DAAS MCP server + CLI - hosts the alerts, cron, composite, daas, dashboard, leader, pdf, and research tool groups (~187 tools) behind one stdio FastMCP server and one Click CLI. Both consume fd_daas_mcp/registry.py so the server and CLI surfaces cannot drift.
Quickstart
This one is not published to a package registry, so there is no one-line install: it is built and started the way its own source says.
Publishernot claimed
FIAll 1 server
finddataofficial1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Fd Daas as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This one is not published to a package registry, so there is no one-line install: it is built and started the way its own source says.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source is public, though no licence is declared for it
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Fd Daas or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 93 / 100
Release 0.1.1 · scanned 14 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score93
Findings11 threat · 10 capability
Capabilityhigh
Coveragesource
Verificationrepo
Surface digestc50a07638d5a6bd202f787061b23cf530eaf7fe1577a9f9b0522cebb7172bf49
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (50 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
The source has registrations with unknown names: the tools registered at fd-daas-mcp/composite-mcp/composite_tools.py:165, fd-daas-mcp/composite-mcp/selfcheck.py:106, fd-daas-mcp/composite-mcp/selfcheck.py:120 and 3 more get their names only at run time (a loop over a list the code builds, a name it computes), so they are not in this surface and were not analysed. To see them, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_series | no tags | |
| get_series_latest | no tags | |
| create_alert_rule | no tags | |
| list_alert_rules | no tags | |
| get_alert_rule | no tags | |
| update_alert_rule | no tags | |
| delete_alert_rule | no tags | |
| list_channels | no tags | |
| run_alert_rule | no tags | |
| list_events | no tags | |
| akshare | no tags | |
| list | no tags | |
| create | no tags | |
| list_upstreams | no tags | |
| add_upstream | code-exec | code-exec: parameter "command" |
| remove_upstream | no tags | |
| list_available_tools | no tags | |
| add_tool | no tags | |
| remove_tool | no tags | |
| list_tools | no tags | |
| add_chained_tool | no tags | |
| remove_chained_tool | no tags | |
| list_chained_tools | no tags | |
| create_manifest | no tags | |
| update_manifest | no tags | |
| delete_manifest | no tags | |
| list_manifests | no tags | |
| create_schedule | no tags | |
| list_schedules | no tags | |
| get_schedule | no tags | |
| delete_schedule | no tags | |
| pause_schedule | no tags | |
| resume_schedule | no tags | |
| run_now | no tags | |
| list_executions | no tags | |
| list_tasks | no tags | |
| create_task | untrusted-inputcode-exec | untrusted-input: keyword "fetch"; code-exec: parameter "command" |
| delete_task | no tags | |
| list_db_tasks | no tags | |
| update_task | code-exec | code-exec: parameter "command" |
| list_databases | no tags | |
| query_table | no tags | |
| list_datasources | no tags | |
| get_executions | no tags | |
| get_stats | no tags | |
| register | no tags | |
| get | no tags | |
| search | no tags | |
| update | no tags | |
| delete | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digestc50a07638d5a6bd2
Scanned2026-10-14
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
It installs from its repository rather than from a versioned package, so the command cannot be pinned to a release. The history below is for reading; the current release on file is 0.1.1.
0.1.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Fd Daas can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.