Skip to main content
Glama
Sign In
kjgueye

netintel-mcp

by kjgueye
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to netintel-mcp

No user-submitted related servers found.

    Related Servers

    • x402farm-mcp

      laurenthalbrun
      A
      license
      Not graded
      quality
      F
      maintenance
      MCP server that provides AI agents with pay-per-call access to a suite of tools (honeypot check, token market, DeFi yields, etc.) via USDC on Base using the x402 protocol.
      5 npm
      MIT

    • Agent Kiosk

      ralf9090
      A
      license
      B
      quality
      C
      maintenance
      Pay-per-call MCP and x402 v2 server on Base USDC providing 19 keyless tools for AI agents: web extraction, social and academic search, B2B lead and domain intelligence, npm/PyPI package and smart-contract security audits, OFAC compliance screening, and DeFi swap quotes
      5
      23
      MIT

    • x402-bazaar-mcp

      sukrutkrdg
      A
      license
      B
      quality
      A
      maintenance
      MCP server exposing x402 Bazaar's paid Base APIs (token risk/honeypot, prices, gas, wallet intel, tx decode + AI utilities) as agent tools. Your agent pays per call in USDC over x402 — no API keys, no signup.
      17
      115 npm
      MIT

    • alderpost-mcp

      8randonpickart5
      A
      license
      A
      quality
      F
      maintenance
      MCP server for Alderpost Intelligence API — 8 x402 endpoints bundling premium data sources (VirusTotal, People Data Labs, Hunter.io, AbuseIPDB, SSL Labs, NIH RxNorm) into scored intelligence responses. Pay per call via USDC on Base.
      8
      17 npm
      2
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.8/5.0

    Scored across 127 tools

    Disambiguation2/5

    Massive overlap across tool families: ~15 near-identical OpenAI model wrappers (netintel_openai, netintel_openai_gpt_4_1, ..._mini, ..._nano, ..._5_x), four translate variants, and several near-duplicate domain/IP/SSL report tools (netintel_domain_report vs netintel_domain_report_full vs netintel_domain vs netintel_domain_vet). Descriptions cross-reference each other helpfully, but boundaries are genuinely fuzzy in many places.

    Naming Consistency3/5

    Consistent netintel_ prefix and mostly snake_case, but the verb/noun ordering is mixed (netintel_ip_geo vs netintel_text_summarize vs netintel_domain_report). Singular/plural and version drift also appear (netintel_prediction_market vs netintel_prediction_markets; netintel_embeddings vs netintel_v1_embeddings; netintel_openai vs netintel_openai_gpt_4_1).

    Tool Count1/5

    127 tools is an extreme over-scoping for any single server, far past the 50+ threshold. Many are redundant model/endpoint variants that would be better served by a parameterized model argument rather than distinct tools.

    Completeness4/5

    Coverage is very broad — IP, domain, DNS, SSL, email, text/data extraction, finance, crypto, weather, search, and even a routing subsystem — with individual, batch, and aggregate-report tiers. Gaps are hard to find; the issue is redundancy rather than missing operations.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources