mcp server
OnchainDiligence
Pay-per-call compliance via x402: wallet sanctions, OFAC name, UK + US company verification.
Description as published by the maintainer. Source
- version 1.1.0
- active
- security
active — Most recent push to the repository was 2026-07-08. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 0 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-07-08 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 0 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 1.1.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-06-27 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-06-27 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub |
Where to get it
Related, by what their authors tagged them
-
Brazilayer — Brazilian Public Data
— last commit 2026-07-27, shares sanctions, x402
Brazilian company registry (CNPJ) + sanctions screening for AI agents. Pay per call via x402.
-
io.github.cyanheads/sanctions-screening-mcp-server
— last commit 2026-07-30, shares sanctions
Screen names against OFAC, EU, UK, UN sanctions lists; resolve entities via GLEIF. Screening aid.
-
io.github.Deep-Identity-Inc/agent-skill
— last commit 2026-07-13, shares sanctions
An MCP Server that provides identity verification and anti-fraud tools for AI agents via deepidv.
-
io.github.clicksprotocol/mcp-server
— last commit 2026-07-21, shares sdk, x402
Agent commerce settlement tools on Base: treasury setup, payment splits, yield and attribution.
-
com.beacio/mcp
— last commit 2026-07-30, shares sdk
MCP server for Web Bluetooth on iOS Safari: scaffolding, UUID lookup, extension detection.
-
com.extentos/mcp-server
— last commit 2026-08-01, shares sdk
Build smart-glasses apps with AI agents: scaffold, validate, and simulate before real hardware.
-
LayerCall
— last commit 2026-08-04, shares sdk
Score an IP, email, phone, domain or device for fraud in one call, with the signals behind it.
-
Mailrith Email Marketing
— last commit 2026-07-31, shares sdk
Manage Subscribers, Broadcasts, Sequences, Automations, and reporting in Mailrith.
-
com.mnemopay/sdk
— last commit 2026-06-26, shares sdk
Memory + wallet for AI agents. Real payment rails, Agent FICO 300-850, Merkle audit, identity.
-
nlqdb — analytical memory for AI agents
— last commit 2026-08-06, shares sdk
Analytical memory for AI agents: a real Postgres queried in plain English over MCP. One command.
These share tags the maintainers applied themselves, such as sanctions, x402, sdk. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.
This is not a recommendation and not a test result. It is a map of what the authors said their work is about.
How the author describes it
Topics the maintainer set on GitHub: compliance, sanctions, sdk, web3, x402.
Bring your own setup
We take apart real AI setups every week and show what broke, what cost too much, and what the trace actually said. If you run agents on real work, that is where the useful conversation is.
Join ZBS AI Practice Lab