Synthex Forge — x402 Paid Agent Services

Run Mcp Security Scan

run_mcp_security_scan

Read-onlyIdempotent

The aggregate MCP-server assessment — ONE signed report. use it rather than run_agent_security_scan for mcp security scan, not agent security scan; an object with 8 fields including files, permissions. $1 USDC.

Input Schema

Name	Required	Description
`task`	No	The task this operation operates on. See the schema for its type and whether it is required.
`text`	No	The source text the operation operates on.
`files`	No	The files this operation operates on. See the schema for its type and whether it is required.
`tools`	No	The tools this operation operates on. See the schema for its type and whether it is required.
`subject`	No	The subject the operation is applied to — an id, a URL or a name, depending on the operation.
`permissions`	No	The permissions this operation operates on. See the schema for its type and whether it is required.
`tool_definitions`	No	The tool definitions this operation operates on. See the schema for its type and whether it is required.
`tool_descriptions`	No	The tool descriptions this operation operates on. See the schema for its type and whether it is required.

Output Schema

Name	Required	Description
`task`	No	The `task` field of the response.
`text`	No	The `text` field of the response.
`files`	No	The `files` field of the response.
`tools`	No	The `tools` field of the response.
`subject`	No	The `subject` field of the response.
`permissions`	No	The `permissions` field of the response.
`tool_definitions`	No	The `tool_definitions` field of the response.
`tool_descriptions`	No	The `tool_descriptions` field of the response.

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 schema fields changedOct 31, 2026

addedOutput schema / properties / files

Added value: +{
+  "description": "The `files` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / permissions

Added value: +{
+  "description": "The `permissions` field of the response.",
+  "type": "object"
+}

removedOutput schema / properties / status

Removed value: -{
-  "type": "string"
-}

addedOutput schema / properties / subject

Added value: +{
+  "description": "The `subject` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / task

Added value: +{
+  "description": "The `task` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / text

Added value: +{
+  "description": "The `text` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / tool_definitions

Added value: +{
+  "description": "The `tool_definitions` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / tool_descriptions

Added value: +{
+  "description": "The `tool_descriptions` field of the response.",
+  "type": "object"
+}

addedOutput schema / properties / tools

Added value: +{
+  "description": "The `tools` field of the response.",
+  "type": "object"
+}

AddedOct 31, 2026

TDQS

A3.9/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already establish that this is a read-only, idempotent, non-destructive operation. The description adds useful behavioral context beyond that — it produces ONE signed report, returns an object with 8 fields, and costs $1 USDC — though it omits any auth, rate-limit, or failure-mode details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is compact and front-loads the main purpose, but the sentence is fragmented and run-on, with lowercase sentence starts and semicolon-separated clauses. The content is reasonably efficient, but the structure makes it harder to parse than necessary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has annotations, a full schema, and an output schema, so the description does not need to explain return values or safety. Still, for an 8-parameter aggregate assessment tool, it leaves important input semantics underexplained and the phrase 'object with 8 fields including files, permissions' is ambiguous.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema is nominally the primary parameter documentation. The description only mentions that the object has 8 fields including `files` and `permissions`, adding little meaning beyond the schema and not explaining how inputs like `task`, `tools`, or `tool_definitions` should be populated.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies a specific resource — an aggregate MCP-server security assessment producing one signed report — and explicitly distinguishes it from `run_agent_security_scan`. The phrasing is awkward and noun-heavy rather than using a clean verb, but an agent can still tell what the tool is for and which sibling not to use.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit routing rule: use this rather than `run_agent_security_scan` for an MCP security scan, not an agent security scan. That names the alternative and the condition that selects it, leaving little ambiguity.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Synthex Forge — x402 Paid Agent Services tools Inspect

Try in Browser

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

Glama MCP Gateway

Add one secure layer between your agents and this server.