io.github.HeyZod/fylings
REMOTE · WWW.FYLINGS.COM · SCANNED SEP 20
Search, verify & screen 1M+ African companies + their government contracts across 18 registries.
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 → Why this is hard to score →
Endpoint Security71
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 403, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
How do I install the io.github.HeyZod/fylings MCP server?
io.github.HeyZod/fylings is a hosted endpoint at https://www.fylings.com/api/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 · www.fylings.com
claude mcp add --transport http heyzod-fylings 'https://www.fylings.com/api/mcp'
{
"mcpServers": {
"heyzod-fylings": {
"url": "https://www.fylings.com/api/mcp"
}
}
} {
"servers": {
"heyzod-fylings": {
"type": "http",
"url": "https://www.fylings.com/api/mcp"
}
}
} [mcp_servers.heyzod-fylings] url = "https://www.fylings.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"heyzod-fylings": {
"type": "remote",
"url": "https://www.fylings.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add heyzod-fylings --url 'https://www.fylings.com/api/mcp' --transport streamable-http
mcp_servers:
heyzod-fylings:
url: "https://www.fylings.com/api/mcp" {
"McpServers": {
"heyzod-fylings": {
"Transport": "http",
"Url": "https://www.fylings.com/api/mcp"
}
}
} assistant mcp add heyzod-fylings -t streamable-http -u 'https://www.fylings.com/api/mcp'
{
"mcpServers": {
"heyzod-fylings": {
"type": "http",
"url": "https://www.fylings.com/api/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.
- 5 Sept 26 −52
- Endpoint reachability: reachable → behind authorisation ▼ security
- Authorization: unverified → fail ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HTTPS: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- HSTS header: pass → fail ▼ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 26 Aug 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Aug 26 0
- Tool “search_companies” rewrote its description, which is the text the model reads security
- Schema quality: 84 → 101 ▼ functional
- 11 Aug 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
- 31 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
- 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
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 20 Sept 2026 · Probed https://www.fylings.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=fylings.com | CN=WE1,O=Google Trust Services,C=US | 23 Jul 2026 | 21 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 3e40775cc73aa7b80e65de57ab0080a6 |
| SANs: fylings.com, *.fylings.com | ||||||
| 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 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.fylings.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| fylings.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On connection |
| HTTP status | 403 |
| Header | Value |
|---|---|
| x-frame-options | SAMEORIGIN |
| referrer-policy | same-origin |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.fylings.com/api/mcp | Auth required | 403 | |
| http (plaintext) | http://www.fylings.com/api/mcp | Inconclusive | 403 |
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_company Get a company record ~75
Fetch one company's full record by country code and registration number, legal name, status, entity type, incorporation date, registry source, and any officers held.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO-2 country code, e.g. NG. |
| registration_no | string | yes | The registry number (RC / RCCM / file no.). |
No output schema declared.
No examples provided.
get_company_procurement Get a company's government contracts ~74
List the government procurement contracts a company has won (from open-contracting data): the awarding body, contract title, value and date. Strong signal of what a company actually does.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO-2 country code, e.g. NG. |
| registration_no | string | yes | The registry number. |
No output schema declared.
No examples provided.
screen_sanctions Sanctions screening ~53
Screen a company or person name against the OFAC SDN, OFAC Consolidated and UN Security Council lists. Returns any matches with a name-match confidence.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The name to screen. |
No output schema declared.
No examples provided.
search_companies Search African companies ~204
Search verified companies across 18 African registries by name or registration number, results are ranked by quality (listed and best-detailed companies first). Matching is tolerant: parent or brand names (Nestlé S.A., AB InBev), typos and word order resolve to the local registered name, and each result carries match_type (id, prefix, contains, normalized, alias, fuzzy) with a 0-1 match_score. An empty result includes suggestions (closest names held). Returns each match's legal name, registration_no, country, status and registry source, plus the total count. To get the full record of any result, call get_company with that result's country and registration_no.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Optional ISO-2 country code to scope the search (e.g. NG, KE, SN). |
| limit | number | – | Max results (default 10). |
| query | string | yes | Company name or registration number to search for. |
No output schema declared.
No examples provided.
What is the io.github.HeyZod/fylings MCP server?
io.github.HeyZod/fylings is an MCP server listed in the public MCP registry as io.github.HeyZod/fylings. Search, verify & screen 1M+ African companies + their government contracts across 18 registries. This page covers its hosted endpoint (https://www.fylings.com/api/mcp).
Is the io.github.HeyZod/fylings MCP server safe to use?
io.github.HeyZod/fylings scores 28 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 io.github.HeyZod/fylings MCP server expose?
io.github.HeyZod/fylings exposes 4 tools: search_companies, get_company, get_company_procurement, screen_sanctions. Their descriptions and schemas cost roughly 406 tokens of context every time the server is loaded.
Does the io.github.HeyZod/fylings MCP server require authentication?
Yes. io.github.HeyZod/fylings asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.github.HeyZod/fylings MCP server still maintained?
io.github.HeyZod/fylings is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.