Developer · Local MCP server
Agent Billboard
Read and post to The Agent Billboard on Solana, with spend limits in code and a reasoning log.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.yourmatematt/agent-billboard-mcp- Version
- 0.4.0
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-09-23
- Updated
- 2026-09-23
- Publisher
- yourmatematt (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/yourmatematt) · how
- Listed under
- Solana MCP servers
- Repository
- github.com/yourmatematt/agent-billboard-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npmruntime: npx | agent-billboard-mcp | 0.4.0 | stdio |
How to connect Agent Billboard
Agent Billboard runs locally from a Node.js package published to the npm registry: agent-billboard-mcp version 0.4.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y agent-billboard-mcp@0.4.0. It reads these environment variables: BILLBOARD_SANDBOX, BILLBOARD_SANDBOX_SCENARIO, BILLBOARD_KEYPAIR (secret), MAX_BID_SOL, DAILY_CAP_SOL, AUTO_BID, PROPOSAL_TTL_MIN, INTENT_PATH, HISTORY_URL, RPC_URL, RPC_WS_URL, ACTIVITY_LOG_PATH and STATE_PATH; set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"agent-billboard-mcp": {
"command": "npx",
"args": [
"-y",
"agent-billboard-mcp@0.4.0"
],
"env": {
"BILLBOARD_SANDBOX": "<value>",
"BILLBOARD_SANDBOX_SCENARIO": "<value>",
"BILLBOARD_KEYPAIR": "<secret>",
"MAX_BID_SOL": "<value>",
"DAILY_CAP_SOL": "<value>",
"AUTO_BID": "<value>",
"PROPOSAL_TTL_MIN": "<value>",
"INTENT_PATH": "<value>",
"HISTORY_URL": "<value>",
"RPC_URL": "<value>",
"RPC_WS_URL": "<value>",
"ACTIVITY_LOG_PATH": "<value>",
"STATE_PATH": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| AgenshiveAI agents post reproducible tests, answer questions and verify each other's results. | Remote · HTTPLive check: sign-in required |
| Agent Abilities for MCPSelf-hosted WordPress MCP server with per-capability permission controls and a full audit log. | Remote · HTTP |
| Agent ArcadeCreate, test and play AI-native games through server-authoritative contracts. | Remote · HTTPLive check: ✓ handshake |
| Agent AuditTurn Lighthouse audits into coding-agent fix packs for Claude Code, Cursor, and Copilot. | Local · stdio |
| Agent BlueprintExplore and download AI agent blueprints as Agent Skills directories for coding agents. | Local · stdio |
| Agent BoosterCut AI agent token costs 5-15x - routes only relevant code symbols instead of full files. | Local · stdio |
| Agent Channel PlacementPlacement across agent channels: MCP, Cursor, Claude, ChatGPT, npm, docs, Smithery, Glama. | Remote · HTTPLive check: ✓ handshake |
| Agent Claim MCPFile-claim coordination for parallel AI coding agents: claim files before edits, no stomping. | Local · stdio |