A
licenseA
qualityB
maintenanceThe safety layer that checks a DeFi transaction or token before your agent (or you) signs — on Base L2.
6
66
MIT
Wolfpack Intelligence
Server Details
On-chain security and market intelligence for trading agents on Base.
If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
4 tool updates
- Removed
mega_report - Removed
narrative_momentum - Removed
smart_money_signals - Removed
trade_signals
1 tool update
- Removed
kol_alpha_tracking
2 tool updates
- Added
kol_alpha_tracking - Added
trade_signals
1 tool update
- Changed
graduation_readiness_check1 field changed- removed
Input schema / properties / tierRemoved value: -{ - "description": "Check tier: \"lite\" (metadata only, $0.01) or \"full\" (live test fires, $1.00). Default: lite", - "type": "string" -}
1 tool update
- Added
agent_credit_risk_index
1 tool update
- Added
graduation_readiness_check
5 tool updates
- Added
il_calculator - Added
mega_report - Added
prediction_market - Added
technical_analysis - Added
yield_scanner
2 tool updates
- Added
smart_money_signals - Added
token_market_snapshot
4 tool updates
- First observed
agent_trust_score - First observed
narrative_momentum - First observed
security_check - First observed
token_risk_analysis
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Pay-per-call crypto market intelligence for AI agents. USDC on Base via x402.
Market data and web intelligence for AI agents, paid per call in USDC on Base via x402.
Read-only on-chain intelligence for AI agents on Base: balances, tokens, gas, tx status.
Read-only on-chain intelligence for AI agents on Base: balances, tokens, gas, tx status.
51
Related MCP Servers
AgentRiskofficial
FlicenseNot gradedqualityBmaintenancePre-Trade Security & Risk Analysis Layer for Autonomous DeFi Agents on Base using x402 protocol.-- FlicenseNot gradedqualityDmaintenancePay-per-use AI security and research tools for autonomous agents on Base, enabling honeypot detection, risk assessment, wallet analysis, and yield optimization via the x402 protocol.-
- AlicenseNot gradedqualityCmaintenanceEnables agents to assess counterparty risk, token danger, and wallet creditworthiness on Base by analyzing contract powers and controlling wallet reputation.MIT
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.9/5.0
Disambiguation4/5
Most tools have distinct purposes, such as agent_credit_risk_index for credit scoring and token_market_snapshot for market data. However, there is some overlap between security_check and token_risk_analysis, both involving token security, which could cause confusion. The descriptions help differentiate them, but the boundaries are not entirely clear.
Naming Consistency3/5
The naming is mixed with some consistency in using snake_case (e.g., agent_credit_risk_index, graduation_readiness_check), but there are deviations like il_calculator and yield_scanner that use different styles. The verbs vary (e.g., 'calculate', 'check', 'scanner'), making it readable but not fully predictable.
Tool Count5/5
With 10 tools, the count is well-scoped for a server focused on crypto and agent intelligence. Each tool appears to serve a specific function within this domain, such as risk analysis, market data, and agent scoring, without feeling excessive or insufficient.
Completeness4/5
The toolset covers key areas like agent analysis, token assessment, and market tools, providing a broad surface for crypto intelligence. Minor gaps exist, such as no direct tools for portfolio management or transaction execution, but agents can likely work around these with the available data and analysis tools.