Nomos MCP Server

pro.nomosPublished by nomos.proOfficial publisherv1.0.0Updated Oct 24, 2026

Dados legislativos e regulatórios do Brasil: proposições, DOU, BACEN, CVM e agências reguladoras

VerifiedStreamable HTTPWeb executableData & Analytics

Overview

AI-generated overview

Remote MCP server giving assistants access to Brazilian legislative and regulatory data, including propositions, DOU, BACEN, CVM and regulatory agencies.

What you can do
Query Brazilian legislative and regulatory data sources, including propositions, the DOU, BACEN, CVM and regulatory agencies. No individual tools are listed, so the exact operations are not documented; the server is described only as a data source for these Brazilian public records.
When to use it
Useful when an assistant needs Brazilian legislative or regulatory information, such as tracking propositions or material from the DOU, BACEN, CVM and regulatory agencies, without building separate integrations.
Requirements
A remote MCP endpoint reached over streamable HTTP. Authentication is required: OAuth plus an X-API-Key header carrying a Nomos API key, which the provider says can be requested through its documentation or team.
Before you install
You must supply a Nomos API key as the X-API-Key header; keep it secret and check the provider's terms for how queries and data are handled. No tools are listed, so verify what the server can read or change before relying on it.

Installation

In SourceWeft

  1. Open Nomos MCP Server 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/pro.nomos%2Fnomos-mcp/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": {
    "nomos": {
      "type": "http",
      "url": "https://mcp.nomos.pro/mcp"
    }
  }
}

README

This repository has no README.

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 16, 2026

Score

60% 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.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Nomos integrations

NOMOS Cross-Border Broker

Published by GitHub account AgentNOMOS

Lets an assistant run cross-border data compliance preflight, read market and tool-catalog data, and get x402 quotes and audit records.

Streamable HTTPWeb executable
Finance5 toolsOct 24, 2026