Peaje

com.usepeajePublished by usepeaje.comOfficial publisherv1.0.0Updated Oct 29, 2026

Your Peaje agent: tasks to get your site cited by AI, its score, and answers about your business.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Peaje is a remote MCP server that gives an assistant access to your Peaje agent: AI-citation tasks for your site, its score, and answers about your business.

What you can do
  • Retrieve the tasks Peaje generates to help get your site cited by AI assistants.
  • Check the score Peaje assigns to your site.
  • Ask questions about your business and get answers from your Peaje agent.
When to use it
Useful if you already work with Peaje on AI visibility and want an assistant to pull your citation tasks, check your score, or answer questions about your business without leaving the chat.
Requirements
A remote MCP endpoint at api.usepeaje.com reached over streamable HTTP, with OAuth sign-in required. No environment variables or headers are declared; a Peaje account is implied by the OAuth flow.
Before you install
Access is tied to your Peaje account through OAuth, so the assistant can read whatever that account exposes. The description does not state whether tasks can be created or changed, so treat any write behavior as unverified. Business details you ask about are sent to Peaje's service.

Installation

In SourceWeft

  1. Open Peaje 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.usepeaje%2Fpeaje/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": {
    "peaje": {
      "type": "http",
      "url": "https://api.usepeaje.com/_owner/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. v1.0.0LatestOct 29, 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.