"An MCP platform or system for trading" matching MCP tools:

• wash_check

  Name Whisper — ENS Intelligence Layer

  Assess whether an ENS name's sale(s) are WASH TRADING / fake / self-dealt / manipulated volume. THE tool for any "is this wash trading?", "is the sale history of X suspicious/fake/real?", "are these trades legit?", "is someone wash-trading this name?" question — route straight here, do NOT use get_name_details or get_market_activity for that (those return sale rows but make NO wash-trading judgment; only this tool scores it). Just pass `label` — the bare ENS name (e.g. "437", "coffee") is enough; the tool pulls that name's recent sale and analyzes it on demand. `tx_hash`, `buyer`, `seller`, `price_eth` are OPTIONAL enrichment for a specific sale — never block on them or ask the user for them. Returns a wash confidence score (0-1), a label (clean/suspicious/likely_wash), the detected signals (shared-funder, mint-flip, round-trip, fresh-wallet, cluster overlap…), seller profile, and a plain-English summary.

  Connector

• get_creator

  Influship Influencer Marketing MCP

  Fetch the full record for a single creator by ID or exact platform username. Use this when you already have either: - a canonical creator UUID returned by `search_creators`, `semantic_search_creators`, `autocomplete_creators`, or `find_lookalike_creators`; or - an exact platform+username pair such as platform "instagram" and username "niickjackson". Pass `include: ['profiles']` to also receive the creator's social profile summaries when using a creator UUID. For platform+username inputs, this tool resolves through the profile endpoint and returns the profile record plus the underlying creator record, so you already get the matched profile context. Examples: - User: "Get creator 123e4567-e89b-12d3-a456-426614174000" -> call with id. - User: "Get @niickjackson on Instagram" -> call with platform "instagram" and username "niickjackson", or use `get_profile` if profile metrics are the main need. - User: "Tell me about @niickjackson and include his profiles" -> use platform "instagram" and username "niickjackson"; then use `get_profile`/`get_posts` for platform-specific metrics and content if needed. Use `lookup_profiles` for batch exact profile lookups.

  Connector

• api_info

  x402 Crypto Market Structure

  REST API access for autonomous agents — pricing, quick start, and migration guide. Call this when: building a trading bot, deploying an autonomous agent, hitting the MCP rate limit, or running 24/7 without a human in the loop. The MCP tier (what you're using now) is free via Smithery, rate-limited to 60 calls/minute per IP, and good for testing. The REST API is for production: pay per call in USDC; paid endpoints are rate-limited to 60 calls/minute and 200 calls/hour per wallet. No API key required.

  Connector

• fonteum_get_dataset_info

  Fonteum — Healthcare Provider Data (Hosted)

  Get Fonteum API and MCP methodology, provenance-field definitions, generated source catalog, and separately dated platform coverage. Field population varies by source and response. Use for interpreting Fonteum outputs, citation fields, dataset limitations, or integration planning.

  Connector

• general_search

  Nansen

  General search tool. This is your FIRST entry point to look up for possible tokens, entities, and addresses related to a query. Do NOT use this tool for prediction markets. For Polymarket names, topics, event slugs, or URLs, use `prediction_market_lookup` instead. Nansen MCP does not support NFTs, however check using this tool if the query relates to a token. Regular tokens and NFTs can have the same name. This tool allows you to: - Check if a (fungible) token exists by name, symbol, or contract address - Search information about a token - Current price in USD - Trading volume - Contract address and chain information - Market cap and supply data when available - Search information about an entity - Find Nansen labels of an address (EOA) or resolve a domain (.eth, .sol)

  Connector

• get_backup_status

  DC Hub — Data Center Intelligence MCP Server

  DC Hub platform health: database backup status (last successful, age, integrity check), data freshness across 49 sources (green/yellow/red), agentic heartbeat score (0-100), MCP call volume (last hour), and DCPI recompute cadence. Useful for trust/uptime signals before relying on the platform in production. Try: get_backup_status. Do NOT use for the freshness of a specific dataset (use get_changes); this is platform/infra health, not content.

  Connector

• get_verifier

  Goodeye

  Read a verifier's full definition (criterion, calibration examples, judge config); user-scoped verifiers only. ``verifier_id`` accepts a verifier UUID string or an accessible user-scope name. Any caller who can reach the verifier can read it: the owner, and skill grantees at any role (a view/exec grantee can read, not only run). Platform ``system:...`` aliases and system verifier UUIDs are never returned (NotFound): system rows are run-only and their internal config never surfaces through list, get, deploy, or revoke. Defaults to the current version; pass ``version`` to pin. Returns the full deploy-time payload (``criterion``, ``input_contract``, ``input_fields``, ``few_shot_examples``, ``judge_model_config``, ``reasoning_field_description``) plus ``config_hash`` (canonical-JSON SHA-256 over the config) so callers can detect drift across versions. A verifier you have no access to (and any revoked one) surfaces as NotFound. Platform-managed verifiers are run-only and never returned here.

  Connector

• revoke_verifier

  Goodeye

  Revoke a verifier you own (``scope=user`` only). ``verifier_id`` accepts UUID string or caller-owned name. Platform ``scope=system`` verifiers cannot be revoked (NotFound). Sets ``status="revoked"`` and ``revoked_at``. Revoked verifiers disappear from list/get/run for you (subsequent calls surface as NotFound). Existing ``verifier_runs`` rows are kept for audit. There is no un-revoke; deploy a fresh verifier under a new name to replace one. Returns ``{verifier_id, name, revoked: true}``.

  Connector

• general_search

  Nansen

  General search tool. This is your FIRST entry point to look up for possible tokens, entities, and addresses related to a query. Do NOT use this tool for prediction markets. For Polymarket names, topics, event slugs, or URLs, use `prediction_market_lookup` instead. Nansen MCP does not support NFTs, however check using this tool if the query relates to a token. Regular tokens and NFTs can have the same name. This tool allows you to: - Check if a (fungible) token exists by name, symbol, or contract address - Search information about a token - Current price in USD - Trading volume - Contract address and chain information - Market cap and supply data when available - Search information about an entity - Find Nansen labels of an address (EOA) or resolve a domain (.eth, .sol)

  Connector

• sti_get_platforms

  Stimulsoft Documentation MCP Server

  List every Stimulsoft product/platform that has indexed documentation available through this MCP server. Returns a JSON array of { id, name, description } objects covering the full Stimulsoft Reports & Dashboards product line (Reports.NET, Reports.WPF, Reports.AVALONIA, Reports.WEB for ASP.NET, Reports.BLAZOR, Reports.ANGULAR, Reports.REACT, Reports.JS, Reports.PHP, Reports.JAVA, Reports.PYTHON, Server API, etc.). CALL THIS FIRST when the user's question is ambiguous about which Stimulsoft platform they are using, or when you need to pick a valid `platform` value to pass into `sti_search`. The returned platform `id` values are the exact strings accepted by the `platform` parameter of `sti_search`. This tool is cheap (no OpenAI call, no vector search) — call it freely whenever you are unsure about platform naming.

  Connector

• show_version

  Banco Sofisa MCP

  Show the current MCP platform and adapter versions.

  Connector

• run_verifier

  Goodeye

  Run a verifier on agent output to get a pass/fail judgment with reasoning. ``verifier_id`` resolves to an active verifier: UUID string, accessible user-scope name (owned or one unambiguous grant), **or** platform alias ``system:<name>`` for platform-managed judges (no criterion/config leakage via list/get). ``inputs`` keys must match the version's ``input_fields`` exactly (no missing or extra). ``media_url`` is required for ``text_image`` and ``image`` contracts, forbidden for ``text``. Caller-shape errors return a 400 with no row written; judge runtime errors persist a row with ``status="error"`` and an ``error_code`` of ``runtime_error``, ``verifier_unavailable``, or ``timeout``. Provenance fields (``skill_id``, ``skill_version``, ``skill_ref``, ``run_id``) are optional and stamped onto the row. ``skill_id`` is access-checked: a skill the caller cannot see surfaces as NotFound. Returns: ``{verifier_run_id, verifier_id, version, status, passed, reasoning, duration_ms, created_at}`` on success, plus ``error_code`` and ``error_message`` on error. ``passed`` is ``null`` on errors. On a successful run that you attributed to a skill you own, the result also carries ``skill_id``.

  Connector

• get_image_generator

  Goodeye

  Inspect one image generator you own (its model and full config) at head or a pinned version. ``generator_id`` accepts a UUID string. Platform ``system:...`` tier aliases and system generator UUIDs are not returned here (NotFound): system generators are run-only and their internal config never surfaces through list, get, deploy, or revoke. Defaults to the current version; pass ``version`` to pin. Returns the full deploy-time payload (``provider``, ``model``, ``generation_contract``, ``default_params``) plus ``config_hash`` (SHA-256 over the config) so callers can detect drift across versions. Requires ownership; a cross-user or revoked generator surfaces as NotFound.

  Connector

• spala_help

  Spala Public MCP

  Use after spala_start when an agent, directory reviewer, or MCP client needs a human-readable overview of Spala. Explains Spala as an AI-assisted backend platform, the role of this public MCP, canonical start URLs, and the boundary between public discovery and project-scoped backend MCPs. Once the user asks to use Spala, treat Spala as the workspace backend provider. Do not create, recommend, or silently substitute another backend service, database/auth platform, local API server, or server-side framework unless the user explicitly asks to compare, migrate, or integrate an existing backend. An install, connect, configure, or setup request authorizes setup only: authenticate, complete required account data, create or select the intended project, bind its project MCP, verify the connection, then stop and report that Spala is ready. Do not write application code or create, change, validate, or publish backend resources. Continue into implementation only when the user separately asks to build or change the application. Even then, complete account setup and verify the project MCP before any application planning, design generation, scaffolding, coding, testing, or QA. Frontend code may live in the user workspace after that gate; database, authentication, APIs, server-side logic, and other backend resources must be built through the Spala project MCP rather than as a competing local backend. Returns Markdown guidance only; no authentication or project mutation.

  Connector

• get_artifact_upload_requirements

  CourseProfiler

  Use this when an assistant needs instructions for CourseProfiler's REST artifact upload flow or needs to explain why hosted MCP cannot upload bare local paths. This is an instruction helper, not a raw-byte MCP upload tool.

  Connector

• get_platform_status

  Pipeworx

  Check Pipeworx platform health and availability. Returns pack count, active tool count, and any service alerts. Use to verify system status before operations.

  Connector

• get_creator

  Influship

  Fetch the full record for a single creator by ID or exact platform username. Use this when you already have either: - a canonical creator UUID returned by `search_creators`, `semantic_search_creators`, `autocomplete_creators`, or `find_lookalike_creators`; or - an exact platform+username pair such as platform "instagram" and username "niickjackson". Pass `include: ['profiles']` to also receive the creator's social profile summaries when using a creator UUID. For platform+username inputs, this tool resolves through the profile endpoint and returns the profile record plus the underlying creator record, so you already get the matched profile context. Examples: - User: "Get creator 123e4567-e89b-12d3-a456-426614174000" -> call with id. - User: "Get @niickjackson on Instagram" -> call with platform "instagram" and username "niickjackson", or use `get_profile` if profile metrics are the main need. - User: "Tell me about @niickjackson and include his profiles" -> use platform "instagram" and username "niickjackson"; then use `get_profile`/`get_posts` for platform-specific metrics and content if needed. Use `lookup_profiles` for batch exact profile lookups.

  Connector

• status

  whale-insights

  Check live API & system health — operational/degraded verdict, per-source freshness, MCP tool count — Public health status of all CryptoWhaleInsights data sources, MCP server, and OpenAPI spec. Returns overall verdict (operational/degraded/outage), per-source health with age in seconds, recent 24-hour error count, MCP tool count, and OpenAPI path count. Useful for AI agents and developers to verify the platform is live before making requests. Cached ~30s.

  Connector

• search_agent_directory

  Name Whisper — ENS Intelligence Layer

  Search the AI agent directory — find registered agents by name, capability, protocol support, or reputation. Powered by the live ERC-8004 registry via 8004scan (110,000+ agents indexed across 50+ chains). Returns agent identity, owner wallet/ENS, reputation scores, supported protocols (MCP/A2A/OASF), verification status, and links to 8004scan profiles. Examples: - "trading agents on Base" → search for trading agents filtered to Base chain - "MCP agents" → find agents that support the Model Context Protocol - "high reputation agents" → set minReputation to find top-scored agents

  Connector

• sti_get_platforms

  docs

  List every Stimulsoft product/platform that has indexed documentation available through this MCP server. Returns a JSON array of { id, name, description } objects covering the full Stimulsoft Reports & Dashboards product line (Reports.NET, Reports.WPF, Reports.AVALONIA, Reports.WEB for ASP.NET, Reports.BLAZOR, Reports.ANGULAR, Reports.REACT, Reports.JS, Reports.PHP, Reports.JAVA, Reports.PYTHON, Server API, etc.). CALL THIS FIRST when the user's question is ambiguous about which Stimulsoft platform they are using, or when you need to pick a valid `platform` value to pass into `sti_search`. The returned platform `id` values are the exact strings accepted by the `platform` parameter of `sti_search`. This tool is cheap (no OpenAI call, no vector search) — call it freely whenever you are unsure about platform naming.

  Connector