Home / MCP registry index / com.novarithm.www/agent-hub
Novarithm Agent Hub: trust and commerce checks
com.novarithm.www/agent-hub in the official MCP registry.
Endpoint https://gogeta2-u35175.vm.elestio.app/agents/mcp. Source: github.com/Salimyou91/novarithm-agent-services-mcp.
The registry describes it as: Agent trust, pre-purchase risk, deliverable checks, data and SEO tools. Pay per call via x402.
We read its 61 tools on 2026-10-27. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
pricing job_result site_audit_quick site_audit_full test_website test_seo test_security_basics test_checkout verify_delivery check_provider compare_quality vendor_report us_geocode uk_postcode a2a_card_check mcp_probe x402_probe agent_ready_score clone_blueprint email_check domain_email_health evaluate_deliverable verify_attestation eu_ready_check fragrance_check fx_convert fx_timeseries fx_latest pre_purchase_check price_availability recall_search gtin_recall sanctions_screen sanctions_crypto_address seller_reputation seo_technical_audit seo_keywords_content seo_internal_links seo_local_presence geo_ai_visibility seo_full_audit trust_trio verify_usdc_payment usdc_balance vendor_due_diligence invoice_duplicate_check migration_compare incident_timeline data_freshness_check field_provenance_check quote_cost_normalize renewal_cohort_check api_contract_diff declared_ingredient_diff demand_lot_match availability_intersection product_content_impact stock_replenishment_scenarios declared_order_delays reservation_record_check and 1 more
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-novarithm-www-agent-hub)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.
Related
Crypto and Web3 MCP servers · Analytics and SEO MCP servers
| The Stall ai.intuitek.the-stall/the-stall | 200 tools, nothing matched 2026-10-22 |
| SAP MCP Server ai.oobeprotocol.sap.mcp/sap-mcp | 200 tools, nothing matched 2026-10-22 |
| Citiview Agent Market com.citiviewgroup.mcp/agent-market | 200 tools, nothing matched 2026-10-26 |
| ScorpTech x402 API com.it.scorptech/x402 | 200 tools, nothing matched 2026-10-26 |
| Apex Edge — x402-paid machine services dev.pages.nonsynthetic/apex-edge | 200 tools, nothing matched 2026-10-23 |
| io.github.praneeth12098/x402-factory io.github.praneeth12098/x402-factory | 200 tools, nothing matched 2026-10-26 |