CodaURL

com.codaurlPublished by codaurl.comOfficial publisherv0.1.0Updated Nov 5, 2026

URL monitoring for AI agents: manage monitors and read status and incidents. Free or Pro account.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

CodaURL is a remote MCP server that lets an assistant manage URL monitors and read their status and incidents.

What you can do
  • Manage URL monitors: create and maintain the endpoints being watched.
  • Read monitoring status: check the current state of monitored URLs.
  • Review incidents: look up recorded incidents for monitored URLs.
When to use it
Useful when you want an assistant to set up or adjust uptime checks on web URLs and to report on their status and past incidents without leaving the conversation.
Requirements
A remote MCP endpoint at mcp.codaurl.com using streamable HTTP. OAuth authentication is required, so a CodaURL account (free or Pro) is needed. No environment variables or headers are declared.
Before you install
OAuth grants the server access to your CodaURL account, and monitor changes made through the assistant affect live monitoring. The free tier may be limited compared with Pro; check plan limits before relying on it.

Installation

In SourceWeft

  1. Open CodaURL in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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.codaurl%2Fmcp/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "codaurl": {
      "type": "http",
      "url": "https://mcp.codaurl.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestNov 5, 2026

Score

83% 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 listed15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • 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.