Skip to content

Valor Services & Contact MCP server

io.github.valor-mineral-management/services-contactvalor-mineral-managementstreamable-httpv1.0.0Scanned

Explore Valor services and prepare a contact request for the user to review and send on Valor.

6 tools: 2 change things and 4 only read.

Tools: 0 delete, 0 irreversible, 2 write, 4 read.
  • Reads private data · 2
  • Reads text others write · 0
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Valor Services & Contact MCP server can do

The Valor Services & Contact MCP server is published by the GitHub account valor-mineral-management. It has 6 tools. It can create or change data (2 tools: about_valor and prepare_contact_request), but cannot delete data. 4 tools only read.

2 tools read private data (get_engagement_information and get_contact_receipt).

The fixed checks matched 1 finding (credentials-mention). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 21, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 2Claude Code: ask
  • about_valorApproved Valor company facts, independence, mineral.tech®, credentials, and full awards catalog.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...any facts, independence, mineral.tech®, credentials, and full awards catalog."

      What this check looks for
    Description, as the server wrote it
    Approved Valor company facts, independence, mineral.tech®, credentials, and full awards catalog.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • prepare_contact_requestAfter the user asks to contact Valor, prepare a short inquiry and return a private Valor review link.No findings

    Why it is in this group

    • The name "prepare_contact_request" says "request": a word for a change.
    Description, as the server wrote it
    After the user asks to contact Valor, prepare a short inquiry and return a private Valor review link. Leave names, email, phone, and addresses out of the message; the user enters them on Valor. No lead is submitted. The user must open the link themselves, review, and send. Do not open or submit on their behalf. Retrying creates another draft, not another lead.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Only reads 4Show 4 read-only tools
  • find_relevant_serviceMatch a selected situation to Valor services.No findings

    Why it is in this group

    • The name "find_relevant_service" says "find": a word for reading.
    Description, as the server wrote it
    Match a selected situation to Valor services. Select broad categories; do not provide personal information.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_contact_receiptCheck only whether this prepared request was sent.Reads private dataNo findings

    Why it is in this group

    • The name "get_contact_receipt" says "get": a word for reading.

    What it can reach

    • private-dataThe name "get_contact_receipt" says "get" and "contact": it reads contacts.
    Description, as the server wrote it
    Check only whether this prepared request was sent. Requires its secret requestToken. Returns an opaque receipt, never contact details or private company records.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_engagement_informationHow to prepare a contact request, required fields, and engagement boundaries.Reads private dataNo findings

    Why it is in this group

    • The name "get_engagement_information" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "contact": it reads contacts.
    Description, as the server wrote it
    How to prepare a contact request, required fields, and engagement boundaries. No pricing or turnaround promises.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_valor_servicesMineral management and operator back-office services, with audience-specific source links.No findings

    Why it is in this group

    • The name "get_valor_services" says "get": a word for reading.
    Description, as the server wrote it
    Mineral management and operator back-office services, with audience-specific source links.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:12 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://www.onevalor.com/mcp/services/v1: tools/list returned 6 tools to an anonymous client, including about_valor (write), prepare_contact_request (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 info

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http services-contact https://www.onevalor.com/mcp/services/v1
claude mcp add --transport http services-contact https://www.onevalor.com/mcp/services/v1

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__services-contact__get_valor_services",
      "mcp__services-contact__find_relevant_service",
      "mcp__services-contact__get_engagement_information",
      "mcp__services-contact__get_contact_receipt"
    ],
    "ask": [
      "mcp__services-contact__about_valor",
      "mcp__services-contact__prepare_contact_request"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as services-contact. Review it before you use it.

Capability tags behind 2 rules
  • mcp__services-contact__get_engagement_information private-data
  • mcp__services-contact__get_contact_receipt private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.valor-mineral-management/services-contact/verify?hash=65192ef41e6708c7d13ea9a396ddf17e414fe680fbc441fa25568e8f1fee5b5b" | jq -e '.changed == false'

Pinned hash 65192ef41e67, from Nov 21, 2026, 05:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.valor-mineral-management/services-contact/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.valor-mineral-management/services-contact
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.valor-mineral-management/services-contact.svg)](https://radar.anlyon.com/servers/io.github.valor-mineral-management/services-contact)

Source: MCP Registry. Synced Oct 21, 2026, 18:51 UTC.

Valor Services & Contact MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Valor Services & Contact MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Valor Services & Contact MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Valor Services & Contact MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Valor Services & Contact MCP server have?

6 tools: 2 write, 4 read. about_valor, prepare_contact_request, get_valor_services, find_relevant_service, get_engagement_information and get_contact_receipt.

Does the Valor Services & Contact MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Valor Services & Contact MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Valor Services & Contact MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 21, 2026.