Fara
NPM · @PIPEWORX/MCP-FARA · 2 COMPONENTS
FARA (Foreign Agents Registration Act) MCP.
Available components
Last scanned (5 hours ago)
Scores higher than 76% of npm servers
Category Education and Research
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-fara). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 651 tokens (~217/item across 3 items; 3 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 Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.10 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 80
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-fara@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-fara |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-fara/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3635936675 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:6ea060054c37b59f360d74a21ecbcc59da96b7dca7f96f55d057194a43c74dfa9725ad4ce34d29c90608c8558b94374f317afa3ed3ddf8db6b09518bf |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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_registrant_documents ~183
List FARA filings (PDF documents) for a registrant by registration_number (from search_registrants) — registration statements, supplemental statements, informational materials, exhibits, etc. Each row links the document to the specific foreign principal/country it concerns and gives a direct PDF URL. Optionally filter CLIENT-SIDE by document_type or country substring. Results are capped. Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Optional case-insensitive substring filter on the associated foreign-principal country. |
| document_type | string | – | Optional case-insensitive substring filter on document type, e.g. "supplemental", "exhibit", "informational". |
| limit | number | – | Max documents to return (default 50, hard cap 100). |
| registration_number | number | yes | FARA registration number of the registrant (from search_registrants). |
No output schema declared.
No examples provided.
list_foreign_principals ~192
List the FOREIGN principals (foreign governments, parties, companies, individuals) that a given FARA registrant represents — i.e. who a US agent is working for. Addressed server-side by registration_number (get one from search_registrants). Optionally filter the returned set CLIENT-SIDE by country or principal-name substring. Set status="terminated" for former relationships. Returns principal_name, country, registrant_name, registration_date and address. Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Optional case-insensitive substring filter on the principal's country, e.g. "italy", "saudi". |
| name | string | – | Optional case-insensitive substring filter on the foreign-principal name. |
| registration_number | number | yes | FARA registration number of the US agent/firm (from search_registrants). |
| status | string | – | Active or terminated representation. Default "active". |
No output schema declared.
No examples provided.
search_registrants ~225
Search FARA registrants — US agents registered to represent FOREIGN principals (foreign governments, parties, businesses) for lobbying/influence inside the US. FARA has no server-side search, so this fetches the bulk active-registrant dump (~556 rows) once and filters CLIENT-SIDE by a name substring (case-insensitive); results are capped. Set status="terminated" to search the much larger terminated dump (~6,500 rows, ~1.4MB fetched once). Returns each registrant's name, registration_number (use it with list_foreign_principals / get_registrant_documents), address and registration_date. Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max rows to return (default 25, hard cap 100). |
| name | string | – | Case-insensitive substring matched against the registrant name + business name, e.g. "scoyoc", "global", "BGR". Omit to return the first page of all registrants. |
| status | string | – | Which registrant dump to search. Default "active". |
No output schema declared.
No examples provided.
How do I install the Fara MCP server?
Fara runs locally as an npm package, launched with npx -y @pipeworx/mcp-fara. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-fara
claude mcp add pipeworx-io-fara -- npx -y @pipeworx/mcp-fara
What is the Fara MCP server?
Fara is an MCP server listed in the public MCP registry as io.github.pipeworx-io/fara. FARA (Foreign Agents Registration Act) MCP. This page covers its npm package (@pipeworx/mcp-fara).
Is the Fara MCP server safe to use?
Fara scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Fara MCP server expose?
Fara exposes 3 tools: search_registrants, list_foreign_principals, get_registrant_documents. Their descriptions and schemas cost roughly 600 tokens of context every time the server is loaded.
Is the Fara MCP server still maintained?
Fara is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Fara MCP server under?
Fara declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.