_ registry / mcp streamable-http · checked 4h ago

vlayer

https://vlayer.app

Registry code: 6f072fd7c6c88412

api record

HIPAA compliance scanner for healthcare software. Automatically detect PHI exposure, encryption gaps, audit logging issues, and access control violations in your codebase. Scan code, get compliance scores, and receive auto-fix suggestions.

from a public catalogue that lists it, not from the operator

endpoint
https://vlayer.app/mcp
protocol
streamable-http ·2024-11-05
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
876ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 4 tools
1 open 3 never probed 1 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_rules open 4h ago

    List the 143 HIPAA scanning rules from the verification-layer catalog, optionally filtered by category.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "category": {
      "enum": [
        "phi-exposure",
        "access-control",
        "audit-logging",
        "data-retention",
        "encryption"
      ],
      "type": "string",
      "description": "Filter rules by category"
    }
  }
}
    arguments 16 lines
  • get_compliance_score unknown 4h ago

    Get a HIPAA compliance score (0-100) for a code snippet or repository. Higher scores indicate better compliance.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "repo_url": {
      "type": "string",
      "description": "GitHub repository URL to scan"
    },
    "code_snippet": {
      "type": "string",
      "description": "Code to evaluate"
    }
  }
}
    arguments 13 lines
  • scan_code unknown never probed

    Run a representative HIPAA quick-scan over a code snippet using a small built-in pattern subset (not the full catalog). For a complete scan of all 143 rules, use the CLI: npx verification-layer scan ./src

    mcp-tool

    {
  "type": "object",
  "required": [
    "code",
    "language"
  ],
  "properties": {
    "code": {
      "type": "string",
      "description": "Source code to scan"
    },
    "language": {
      "enum": [
        "typescript",
        "python",
        "java"
      ],
      "type": "string",
      "description": "Programming language"
    }
  }
}
    arguments 22 lines
  • suggest_fix unknown never probed

    Get remediation guidance for a specific HIPAA rule by its id, including the recommendation and HIPAA reference.

    mcp-tool

    {
  "type": "object",
  "required": [
    "violation_id"
  ],
  "properties": {
    "code_context": {
      "type": "string",
      "description": "Optional code surrounding the violation"
    },
    "violation_id": {
      "type": "string",
      "description": "Rule ID from the catalog (e.g. enc-des, CRED-002, ssn-hardcoded)"
    }
  }
}
    arguments 16 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/6f072fd7c6c88412/badge.svg)](https://brick.blue/agent/6f072fd7c6c88412)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.