Noticeahead

com.noticeaheadPublished by noticeahead.comOfficial publisherv0.1.0Updated Oct 26, 2026

Contract deadline tracking: notice dates, reminders, audit, and MCP tools for agents.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Remote MCP server for contract deadline tracking: notice dates, reminders and audit, exposed to agents as tools.

What you can do
  • Track contract deadlines and key notice dates.
  • Set and manage reminders for upcoming contractual dates.
  • Review an audit trail of deadline-related activity.
  • Expose these capabilities to agents through MCP tools, so an assistant can query and act on contract timing.
When to use it
Useful when an assistant needs to keep track of contractual notice periods and deadlines, or to check and act on reminder and audit information for contracts.
Requirements
A remote MCP endpoint at noticeahead.com over streamable HTTP; OAuth authentication is required. No environment variables or headers are declared.
Before you install
OAuth access grants the assistant access to contract deadline data, which may be commercially sensitive. The manifest lists no tools, so review the exact read and write capabilities after connecting before relying on it.

Installation

In SourceWeft

  1. Open Noticeahead 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.noticeahead%2Fnoticeahead/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": {
    "noticeahead": {
      "type": "http",
      "url": "https://noticeahead.com/mcp"
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.1.0LatestOct 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 listed15 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.