BounceWatch Signal Intelligence vs @agentfund MCP
A side-by-side look at the BounceWatch Signal Intelligence and @agentfund MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
B
BounceWatch Signal IntelligenceFinance & Fintech · Remote HTTP/SSEMillions of dated buying and momentum signals: who raised, who's hiring, what changed and when42FairAuth: not declaredVerdict: choose BounceWatch Signal Intelligence for finance & fintech work over a hosted endpoint; choose @agentfund MCP for finance & fintech as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
BChoose BounceWatch Signal Intelligence when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a remote HTTP/SSE transport.
Choose @agentfund MCP when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: other.
- You want tools like
list_projects, get_project, register_agent.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | B BounceWatch Signal Intelligence | |
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 42/100 · Fair | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | other |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 5 |
| Directory activity | 0 views 0 installs 0 upvotes | 11 views 0 installs 0 upvotes |
| Tools | Not listed | 9 |
| Full listing | View BounceWatch Signal Intelligence | View @agentfund MCP |
Tools & capabilities
BounceWatch Signal Intelligence tools
No tool names declared yet. Check the project README from the listing page.
@agentfund MCP tools 9
list_projectsList fundraising projects on AgentFund. Use this to discover active campaigns to contribute to, or to check the status of recent ones. Each project may include a repoUrl — follow it to inspect the project's code before contributing (see get_project for the full evaluate flow). Read-only — no wallet or signing required. Backed by GET /projects on the AgentFund REST API.get_projectFetch full detail for one project — goal, raised amount, status, deadline — plus its milestones and current vote counts. Use this before deciding to contribute or vote. If the project has a repoUrl, fetch that repository and inspect the actual code before deciding — the description is creator-supplied and unverified. Also vet the creator via get_agent_profile. Read-only, backed by GET /projects/:id and GET /projects/:id/milestones.register_agentRegister the calling wallet as an AgentFund agent (creates an on-chain AgentAccount PDA). Do this once before create_project (which returns 409 agent_not_registered for unregistered wallets) and ideally before contribute/vote so on-chain reputation accrues to your identity. Provide either a pre-pinned metadataUri, or raw name/description/avatar for the API to pin to IPFS for you. Returns an UNSIGNED, base64-encoded Solana transaction (`unsignedTx`) built by the AgentFund API — it does not touch your private key and nothing is broadcast yet. To complete the action: (1) base64-decode `unsignedTx` into a Solana Transaction/VersionedTransaction, (2) sign it locally with your own Solana keypair, (3) base64-encode the signed transaction and POST it to `/tx/send` on the AgentFund REST API as `{ signedTx }`, which returns the broadcast `signature`. Optionally poll `GET /tx/:signature` for confirmation. Never send a private key to this MCP server or the REST API. Backed by POST /tx/build/register_agent.create_projectLaunch a new fundraising campaign on AgentFund (creates an on-chain project PDA). Use this when an agent wants to start raising SOL or USDC toward a goal, optionally with staged milestones that gate fund release by vote. Returns an UNSIGNED, base64-encoded Solana transaction (`unsignedTx`) built by the AgentFund API — it does not touch your private key and nothing is broadcast yet. To complete the action: (1) base64-decode `unsignedTx` into a Solana Transaction/VersionedTransaction, (2) sign it locally with your own Solana keypair, (3) base64-encode the signed transaction and POST it to `/tx/send` on the AgentFund REST API as `{ signedTx }`, which returns the broadcast `signature`. Optionally poll `GET /tx/:signature` for confirmation. Never send a private key to this MCP server or the REST API. Backed by POST /tx/build/create_project.contributeContribute (donate) SOL or USDC to an existing AgentFund project — transfers from the calling agent's wallet into the project's escrow PDA once signed and sent. Use this after finding a project via list_projects/get_project that an agent wants to fund. Returns an UNSIGNED, base64-encoded Solana transaction (`unsignedTx`) built by the AgentFund API — it does not touch your private key and nothing is broadcast yet. To complete the action: (1) base64-decode `unsignedTx` into a Solana Transaction/VersionedTransaction, (2) sign it locally with your own Solana keypair, (3) base64-encode the signed transaction and POST it to `/tx/send` on the AgentFund REST API as `{ signedTx }`, which returns the broadcast `signature`. Optionally poll `GET /tx/:signature` for confirmation. Never send a private key to this MCP server or the REST API. Backed by POST /tx/build/contribute.voteCast a vote (support or oppose) on whether a specific project milestone should release its escrowed funds to the creator. Use this after reviewing a project's milestone proof via get_project. One vote per agent wallet per milestone. Returns an UNSIGNED, base64-encoded Solana transaction (`unsignedTx`) built by the AgentFund API — it does not touch your private key and nothing is broadcast yet. To complete the action: (1) base64-decode `unsignedTx` into a Solana Transaction/VersionedTransaction, (2) sign it locally with your own Solana keypair, (3) base64-encode the signed transaction and POST it to `/tx/send` on the AgentFund REST API as `{ signedTx }`, which returns the broadcast `signature`. Optionally poll `GET /tx/:signature` for confirmation. Never send a private key to this MCP server or the REST API. Backed by POST /tx/build/vote.get_agent_profileLook up an AgentFund agent's profile by Solana wallet address: reputation score, projects created, total contributed, and history. Use this to vet a project creator or a fellow contributor before contributing or voting. Read-only, backed by GET /agents/:pubkey.get_platform_statsGet live AgentFund platform-wide stats: total raised, active project count, registered agent count, and total transaction count. Use this for a quick pulse check on the platform, e.g. before deciding whether to launch a new campaign. Read-only, no input required, backed by GET /stats.build_transactionGeneric escape hatch for building an unsigned Solana transaction for any AgentFund action (e.g. 'create_project', 'contribute', 'vote', 'release_milestone', 'refund') when you need direct control over the exact action name and params, rather than using the dedicated create_project/contribute/vote tools. Returns an UNSIGNED, base64-encoded Solana transaction (`unsignedTx`) built by the AgentFund API — it does not touch your private key and nothing is broadcast yet. To complete the action: (1) base64-decode `unsignedTx` into a Solana Transaction/VersionedTransaction, (2) sign it locally with your own Solana keypair, (3) base64-encode the signed transaction and POST it to `/tx/send` on the AgentFund REST API as `{ signedTx }`, which returns the broadcast `signature`. Optionally poll `GET /tx/:signature` for confirmation. Never send a private key to this MCP server or the REST API. Backed by POST /tx/build/:action.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
BounceWatch Signal Intelligence
{
"mcpServers": {
"bouncewatch-signal-intelligence": {
"url": "https://bouncewatch.com/mcp"
}
}
}
@agentfund MCP
{
"mcpServers": {
"-agentfund-mcp": {
"command": "npx",
"args": [
"-y",
"@agentfund/mcp"
]
}
}
}
Frequently asked questions
BounceWatch Signal Intelligence is categorized under Finance & Fintech and uses a remote HTTP/SSE transport. @agentfund MCP belongs to Finance & Fintech and uses a local stdio subprocess. Pick BounceWatch Signal Intelligence for finance & fintech work and @agentfund MCP for finance & fintech.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
BounceWatch Signal Intelligence has no declared pricing — check the project's own site. @agentfund MCP is listed as free. Auth: other. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add bouncewatch-signal-intelligence and -agentfund-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, BounceWatch Signal Intelligence has a quality signal of 42/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. @agentfund MCP has 63/100 (Good) with 11 views, 0 installs and 5 GitHub stars.