ManosPay

com.manospayPublished by manospay.comOfficial publisherv1.0.0Updated Oct 27, 2026

Invoices, proposals and payments for contractors. Bilingual (ES/EN). Sign in with ManosPay.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

ManosPay is a remote MCP server for contractor invoicing, proposals and payments, signed in with a ManosPay account.

What you can do
  • The listing names no individual tools, so capabilities are inferred from the description.
  • Work with invoices, proposals and payments for contractor work.
  • Operate in a bilingual Spanish/English context.
  • Access is tied to a ManosPay account via sign-in.
When to use it
Worth considering if you are a contractor or freelancer using ManosPay and want an assistant to help with invoices, proposals and payment-related work inside that account.
Requirements
A remote MCP endpoint at manospay.com reached over streamable HTTP, with OAuth sign-in to a ManosPay account required. No environment variables or headers are declared.
Before you install
The server handles invoices, proposals and payments, so an assistant may be able to create or change billing documents and payment data in your account; review actions before confirming. Sign-in is through OAuth with your ManosPay account, so grant access only to a client you trust. No tool list is published, so the exact scope of what it can read or change is unclear.

Installation

In SourceWeft

  1. Open ManosPay 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.manospay%2Fmanospay/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": {
    "manospay": {
      "type": "http",
      "url": "https://manospay.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. v1.0.0LatestSep 30, 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.