Blackhull trading post: pre-trade checks for agents on Base
com.blackhullsystemsPublished by blackhullsystems.comOfficial publisherv1.1.1Updated Nov 5, 2026
Before your agent buys a Base token: can it sell it back? Plus x402 service grades and providers.
Overview
Remote MCP endpoint that lets an agent run pre-trade checks on Base tokens, including whether a token can be sold back, plus x402 service grades and providers.
- What you can do
- Check a Base token's sellability before an agent buys it, per the description's pre-trade check framing.
- Look up x402 service grades and providers, as stated in the registry description.
- No tool list, instructions or README is supplied, so the exact operations and their inputs are not documented here.
- When to use it
- Worth considering when an agent trades or pays for services on Base and you want a pre-purchase sanity check on a token's ability to be sold back, or context on x402 services and providers.
- Requirements
- A remote streamable HTTP endpoint at the provider's site; no package install. The manifest declares no authentication, environment variables or headers, and no account or key requirements are documented.
Installation
In SourceWeft
- Open Blackhull trading post: pre-trade checks for agents on Base 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/com.blackhullsystems%2Flistening-post/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": {
"blackhull-trading-post-pre-trade-checks": {
"type": "http",
"url": "https://blackhullsystems.com/mcp"
}
}
}Tools
0Version history
3- v1.1.1LatestNov 5, 2026
- v1.1.0Nov 5, 2026
- v1.0.0Oct 30, 2026
Score
17% 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
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
Publish an icon in the registry entry.
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.