Inspection
- List authorized sites and provider health
- Read runs, evidence, findings and proposals
- Inspect usage, failures and activity summaries
Explore SEOForge
Remote MCP
Give approved AI clients evidence access—not production authority.
Remote MCP can expose tenant-scoped inspection and bounded workflow-request tools. The current tool manifest returned by the authorized server is the source of truth; examples here are illustrative.
Nothing publishes without approvalPaid product accessNo ranking guarantees
{
"tool": "findings.list",
"arguments": { "site_id": "site_123" }
}Tool classes
Inspect current state or request bounded work.
Controlled requests
- Request an allowed agent workflow
- Pass an explicit authorized site ID
- Receive a run ID and watch state
- Remain subject to quotas and policy
Authentication
Use a hashed, expiring and revocable site-bound token.
Create tokens inside the signed-in paid workspace, label the client, use TLS, rotate on exposure and never paste provider credentials into client context.
Scopes
Server tool discovery still enforces tenant policy.
A client seeing a tool name does not gain access to every site. Workspace, site, environment and operation restrictions are checked on each call.
Limits
Tool calls consume plan and provider capacity.
Clients must respect structured rate-limit errors, Retry-After guidance and run quotas. Poll with backoff or use webhooks instead of high-frequency empty polling.
Errors
Expect protocol and policy failures separately.
{ "code": "site_scope_denied", "message": "Token is not authorized for site_456", "request_id": "req_example" }No production tools exist
- MCP can never approve or reject a production proposal
- MCP can never merge, deploy or publish
- MCP can never retrieve credentials
- MCP can never bypass human approval or provider protection
Paid deployment · human authority
Connect MCP only inside an authorized paid workspace.
Choose a plan or discuss client, scope and rate-limit requirements with sales.