Gateway

com.edgethirteen.wwwPublished by www.edgethirteen.comOfficial publisherv1.0.0Updated Oct 28, 2026

All 36 Edge Thirteen MCP tools (SEC filings, WCAG, entity diligence, more) in one endpoint.

The publisher's own server: Accessproof

VerifiedStreamable HTTPWeb executableSecurity & MonitoringBusiness & Commerce

Overview

AI-generated overview

Remote MCP endpoint bundling all 36 Edge Thirteen tools, covering SEC filings, WCAG accessibility checks, entity diligence and more.

What you can do
  • Access the full Edge Thirteen tool set through a single remote endpoint.
  • Retrieve and work with SEC filings.
  • Run WCAG accessibility checks.
  • Perform entity diligence research.
  • Use the remaining Edge Thirteen tools, which the listing does not enumerate.
When to use it
Worth adding when you want one connection that exposes the whole Edge Thirteen tool collection, such as regulatory filings, accessibility review and entity research, instead of installing separate servers.
Requirements
A remote streamable HTTP endpoint at the provider's site; no package, environment variables or headers are declared. The listing declares no authentication, so account or key requirements are unclear.
Before you install
The listing does not enumerate the tools or their inputs, so what each one sends or changes is unknown. No authentication is declared, so check the provider's terms and data handling before relying on it for sensitive filings or diligence queries.

Installation

In SourceWeft

  1. Open Gateway in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.edgethirteen.www%2Fgateway/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "gateway": {
      "type": "http",
      "url": "https://www.edgethirteen.com/api/mcp/gateway"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 17, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Edgethirteen integrations