smartflow-verify-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SMARTFLOW_BASE_URL | No | Overrides the API base URL. | https://verify.smartflowproai.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_network_decompositionA | FREE, read-only. Integrity-sealed decomposition of x402 payment growth on Base from SmartFlow Observatory's independent ledger of USDC micro-transfers: how much of the headline volume is wash / self-dealing / clone-fleet activity vs bundler plumbing vs the organic clean core. Returns the full dataset plus |
| order_endpoint_auditA | Creates a PAYABLE ORDER for a $399 signed, human-reviewed audit of an x402 endpoint or receiving wallet (wash-share, payer concentration, demand dispersion, attribution), delivered by email within 48 business hours of payment. COST: calling this tool is free and moves NO funds. It returns an x402 |
| get_audit_order_statusA | FREE, read-only. Poll the status of an audit order created with order_endpoint_audit. Status |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: creating a payable audit order, polling that order's status, and retrieving network decomposition data. The descriptions reinforce the boundaries with explicit sequencing instructions, leaving no realistic chance of misselection.
All three names follow a predictable verb_noun pattern: get_audit_order_status, get_network_decomposition, and order_endpoint_audit. The verbs differ naturally by action, but there is no mixing of casing or naming styles.
Three tools is well-scoped for a focused verification-and-ordering server. Each tool earns its place: one read for decomposition, one order creation, and one status poll for the audit lifecycle.
The audit-order lifecycle is covered through creation and status polling, and decomposition data is separately available. Minor gaps exist, such as no order listing, cancellation, or direct report retrieval, but expiry and email delivery provide reasonable workarounds.