PROME Care Core

ai.promePublished by prome.aiOfficial publisherv5.0.1Updated Oct 24, 2026

Check actions against fixed values using supplied numeric facts. Never authorizes or executes.

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Remote MCP endpoint that checks proposed actions against fixed values using numeric facts you supply, without authorizing or executing anything.

What you can do
  • Check a proposed action against fixed values using numeric facts supplied in the request.
  • Return a pass or fail style verdict for each check, with missing facts or errors reported as such.
  • Never authorizes or executes the action itself; it only evaluates the facts given to it.
When to use it
Useful when an assistant needs a consistent, external rule check on a proposed action before proceeding, and you want the decision kept separate from execution.
Requirements
Remote streamable HTTP endpoint at prome.ai; no local package. Requires a bearer token in the Authorization header: your own RapidAPI key, obtained by subscribing to the PROME Care Core plan on RapidAPI. Each check is billed against that plan.
Before you install
The Authorization header carries your RapidAPI key, so treat it as a secret. Checks consume your paid RapidAPI plan quota. The server only evaluates the facts you provide and does not authorize or execute actions, so do not rely on it as a sole safeguard.

Installation

In SourceWeft

  1. Open PROME Care Core in the dashboard and add it to a workspace.
  2. Connect Authorization token 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/ai.prome%2Fcare-core/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": {
    "prome-care-core": {
      "type": "http",
      "url": "https://prome.ai/api/marketplace-mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

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

2
  1. v5.0.1LatestSep 17, 2026
  2. v5.0.0Sep 16, 2026

Score

67% 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

    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.