
Certvas — African & EM Markets
io.github.KingMandasePublished by GitHub account KingMandasev1.0.2Updated Oct 24, 2026
License-clean African & EM data as citable agent tools: company fundamentals, tenders (OCDS), macro.
Overview
Lets an assistant query licensed African and emerging-market data—company fundamentals, tenders, and macro indicators—as citable tools.
- What you can do
- Certvas exposes African and emerging-market datasets to an assistant as citable tools. According to the registry description, these cover company fundamentals, tenders following the OCDS standard, and macroeconomic data. It is a remote server reached over streamable HTTP, so the assistant calls it directly rather than running anything locally. No individual tool names are listed in the manifest.
- When to use it
- Useful when an assistant needs sourced, citable data on African or emerging-market companies, public procurement tenders, or macro indicators, for example in research, due diligence, or market analysis.
- Requirements
- A remote MCP endpoint over streamable HTTP; nothing runs locally. An API key is required and sent in the x-api-key header; the manifest says a free sample key can be requested from the provider. No environment variables are declared.
Installation
In SourceWeft
- Open Certvas — African & EM Markets in the dashboard and add it to a workspace.
- Connect x-api-key credentials. They are stored privately and never shown on public pages.
- 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.KingMandase%2Fcertvas/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": {
"certvas-african-em-markets": {
"type": "http",
"url": "https://dataco-mcp.northtide.workers.dev/mcp",
"headers": {
"x-api-key": "<YOUR_API_KEY>"
}
}
}
}README
This repository has no README.
Tools
0Version history
1- v1.0.2LatestSep 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 listed15 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.