47620 Solana Data
io.github.47620-xyz/solana-data
Pay-per-call Solana data for AI agents over x402: token, account, tx, trending. No signup, no key.
Remote endpoint
https://47620.xyz/mcpOLACHEAP · MCP WORKSPACE / DEVELOPER
Choose developer MCP servers for one concrete job: reading repositories, tracing pull requests, reviewing code changes, or checking build status. A tool that can search code is not automatically appropriate for merging a pull request.
Results come from the current synchronized Registry snapshot, not popularity or activity.
io.github.47620-xyz/solana-data
Pay-per-call Solana data for AI agents over x402: token, account, tx, trending. No signup, no key.
https://47620.xyz/mcpio.github.48x-ai/marketbasketanalysis-mcp
Co-purchase intelligence and merchant ops tools for AI shopping, ecommerce, and B2B agents
https://mcp.marketbasketanalysis.com/mcpio.github.4DA-Systems/4da-mcp-server
Upgrade intelligence for AI agents: what an upgrade changes, where it touches your code, CVE scans.
io.github.4hmetuyar/a2a-auditor
Scans Agent2Agent (A2A) protocol code for webhook SSRF, missing auth, and credential exposure
io.github.4hmetuyar/agent-graph-auditor
Finds transitive excessive agency across LangGraph/CrewAI/AutoGen orchestration graphs
io.github.4hmetuyar/ai-code-scanner
Scans code for insecure LLM/AI integration: exposed keys, unsafe output, prompt injection
io.github.4hmetuyar/compliance-checker
KVKK/GDPR/CCPA compliance checks for codebases
io.github.4hmetuyar/dependency-auditor
CVE scanning for npm/pip/cargo dependencies via OSV
io.github.4hmetuyar/dns-intelligence
DNS record enumeration, misconfiguration and dangling-subdomain detection
io.github.4hmetuyar/elicitation-auditor
MCP elicitation anti-patterns: secrets in forms, third-party authorize URLs, credentials in URLs
io.github.4hmetuyar/llm-redteam
Active jailbreak/extraction/obfuscation red-teaming for live LLM endpoints
io.github.4hmetuyar/mcp-config-auditor
Scans Cursor/Claude/Windsurf/VS Code MCP configs for unpinned versions, secrets, typosquats
io.github.4hmetuyar/mcp-server-auditor
Scans MCP server tool definitions for excessive agency, injection sinks, hardcoded secrets
io.github.4hmetuyar/memory-poisoning-scanner
Scans agent code for untrusted input poisoning persistent cross-session memory
io.github.4hmetuyar/model-scanner
Scans ML model files (PyTorch, safetensors, Keras, ONNX) for supply-chain risks
io.github.4hmetuyar/oauth-auditor
Scans MCP server auth code for OAuth 2.1 anti-patterns: token passthrough, missing audience
io.github.4hmetuyar/prompt-injection-scanner
Scans RAG content/scraped pages for indirect prompt injection
io.github.4hmetuyar/prompt-leak-scanner
Catches leaked credentials and PII in outbound LLM prompts
io.github.4hmetuyar/rug-pull-detector
Baselines an MCP server's tools and detects tool-definition changes after approval
io.github.4hmetuyar/secret-scanner
Scans files for leaked secrets and API keys
io.github.4hmetuyar/security-proxy
MCP gateway: many servers, one policy, lethal-trifecta blocking, PII masking, audit log
io.github.4hmetuyar/security-suite
Bundle of secret-scanner, dependency-auditor, ssl-inspector, and dns-intelligence
io.github.4hmetuyar/slopsquat-scanner
Checks declared npm/PyPI dependencies against real registries to catch slopsquatting
io.github.4hmetuyar/ssl-inspector
TLS certificate/cipher/protocol inspection
Synchronized data; no invented downloads, reviews or ratings.
OLACHEAP · PRACTICAL GUIDES
Start with a read-only repository and ask the AI client to locate a known file or explain an existing change. Confirm the answer against the actual commit and file path before enabling changes to branches, issues, or CI settings.
Compare the source repository, authentication method, documented scopes, tool descriptions, and whether operations write to a repository. Prefer explicit approval of each merge, push, or deletion, and check which GitHub identity will own the change.
A successful repository search does not prove the server is secure. Treat issue descriptions, code comments, and README content as untrusted input, avoid exposing secrets in logs, and keep the ability to revoke tokens.
Use their exact Registry IDs to compare published connection information before granting permissions.