Jaco Veldsman
Jaco Veldsman operates The MCP Census, a public-evidence gate for Model Context Protocol servers. It checks registry, repository, package, hosted-endpoint and related public evidence and returns PASS, REVIEW, BLOCK or UNKNOWN before an agent installs or connects to a server; it explicitly is not a malware scanner or the official MCP registry.
At a Glance
- Individual developers and coding-agent users
- AI-agent and MCP platform builders
- Engineering and platform teams
- Security and supply-chain teams
- +1 more
AI Tools by Jaco Veldsman
(1)
The MCP Census
MCP Server Pre-Install Checker
Discussions
No discussions yet
Be the first to start a discussion about Jaco Veldsman
Latest News
How to check an MCP server is safe before you install it
OX counted 15,465 public MCP servers with no vetting; MCP Census published its 45,143-server evidence-based comparison
Census stamp vs mcp-scan: comparison of pre-connect public-evidence checks and post-connect tool-description scanning
What changed in MCP 2026-07-28: analysis of the stateless revision and mandatory server/discover capability
Products & Services
A no-signup web lookup that checks an exact MCP server name and presents public evidence and a PASS, REVIEW, BLOCK or UNKNOWN decision.
REST endpoints for search, lookup, stats, preflight, stamps, configuration audits, changes and watches; the service supports keyless usage for selected operations and API-key access for larger workloads.
A streamable HTTP MCP endpoint at https://api.mcpcensus.com/mcp, with tools including census_search, census_preflight, census_stamp, census_audit_config, census_changes and census_credits.
Developer workflows that audit .mcp.json and related client configurations, return one verdict per server, provide an exit code for CI, and support a rule line for agents to run a Census stamp before adding, enabling or calling an MCP server.
Market Position
The MCP Census positions itself as a public-evidence trust and health gate rather than an MCP directory, malware scanner, pen-test, or tool-poisoning scanner. Its comparison content differentiates it from registries and directories such as Glama, Smithery and mcp.so by emphasizing identity, maintenance, package/repository health, remote liveness, evidence links and explicit UNKNOWN outcomes; it complements post-connect scanners such as mcp-scan rather than replacing them.
Leadership
Executive Team
Jaco Veldsman
Operator, The MCP Census
Australian fintech founder and Paytron co-founder; public professional profiles describe Paytron as acquired by OFX, and identify Veldsman in payments, data and AI. The MCP Census legal and About pages identify him as its operator.
Founding Story
The project was created to fill the gap between MCP directories, which establish that a server exists, and an evidence-based installation decision. Its stated initial vision is to continuously re-harvest registry data, check server health and hosted endpoints, cross-reference public adoption evidence, and show the underlying evidence rather than present an unsupported safety guarantee.
Business Model
Revenue Model
A freemium, credit-based model: anonymous users receive limited lookup access; accounts receive monthly credits; paid Builder and Team subscriptions provide recurring credits and features; one-time Packs provide non-expiring credits. The Terms also say higher-volume paid access may be arranged by email.
Pricing Tiers
10 unique lookups per day per IP; stats and selected public operations are unmetered.
1,000 credits per UTC month with an account and API key; no card.
2,000 credits each UTC month; purchased credits never expire; REST, MCP, stamps and watches.
1,000 credits that never expire.
10,000 credits each UTC month; pricing page lists search/lookup, config audit, preflight/stamp and watch allowances.
Target Markets
- Individual developers and coding-agent users
- AI-agent and MCP platform builders
- Engineering and platform teams
- Security and supply-chain teams
- Organizations managing MCP configuration in CI/CD
- Pre-install checks for coding agents and humans
- Auditing MCP configurations before connecting tools
- CI gates for pull requests that change MCP configuration
- Monitoring server health, verification and endpoint changes
- Security and platform-team inventory of MCP supply-chain risk
- Checking whether a server is first-party or a lookalike