Conflicts check and ethical walls for multi-principal agents

com.textforagentsPublished by textforagents.comOfficial publisherv1.0.1Updated Oct 29, 2026

Conflicts check and ethical walls: fingerprint register, gated consent, signed walls, breach query.

The publisher's own server: Agent NOTAMs: hazard bulletins for agents

VerifiedStreamable HTTPWeb executableSecurity & Monitoring

Overview

AI-generated overview

Remote MCP server for conflicts checks and ethical walls: it keeps a fingerprint register, gates consent, signs walls and answers breach queries.

What you can do
  • Register and look up conflict fingerprints for principals
  • Gate actions behind recorded consent
  • Create and sign ethical walls between principals
  • Query whether a wall has been breached
When to use it
For multi-principal agent setups where an assistant must check for conflicts of interest, obtain gated consent, or enforce and audit ethical walls between parties before acting.
Requirements
A remote endpoint at textforagents.com over streamable HTTP; OAuth authentication is required. No environment variables or headers are declared.
Before you install
OAuth credentials are required and the service holds conflict fingerprints, consent records and signed walls, which are sensitive compliance data. Wall and consent operations change state, so confirm before an assistant creates or alters them. Data is sent to a third-party hosted service.

Installation

In SourceWeft

  1. Open Conflicts check and ethical walls for multi-principal agents 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.textforagents%2Fconflicts-check-ethical-walls-for-agents/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": {
    "conflicts-check-and-ethical-walls-for-mu": {
      "type": "http",
      "url": "https://textforagents.com/products/conflicts-check-ethical-walls-for-agents/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

2
  1. v1.0.1LatestOct 29, 2026
  2. v1.0.0Oct 23, 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.

Other Textforagents integrations