
Fylings
io.github.HeyZodPublished by GitHub account HeyZodv1.0.0Updated Oct 24, 2026
Search, verify & screen 1M+ African companies + their government contracts across 18 registries.
Overview
Lets an assistant search, verify, and screen over a million African companies and their government contracts across 18 registries.
- What you can do
- Fylings is a remote MCP server that gives an assistant access to a database of more than one million African companies and their government contracts, drawn from 18 registries. It supports searching for companies, verifying their details, and screening them, so an assistant can look up and cross-check business entities on request. The manifest lists no individual tools, so the exact operations are not documented here.
- When to use it
- Worth adding when an assistant needs to look up, verify, or screen African companies or their public government contracts, for example during due diligence, onboarding, or supplier research. It is not intended for general web search or for company data outside the covered registries.
- Requirements
- A remote MCP endpoint at the provider's site, reached over streamable HTTP. The manifest declares no authentication, no environment variables, and no headers, so no credentials appear to be needed; network access to the endpoint is required.
Installation
In SourceWeft
- Open Fylings in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.HeyZod%2Ffylings/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"fylings": {
"type": "http",
"url": "https://www.fylings.com/api/mcp"
}
}
}README
This repository has no README.
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
60% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.