HRSA Health Resources

com.olyportPublished by olyport.comOfficial publisherv1.0.0Updated Oct 24, 2026

Health professional shortage areas and community health centers

The publisher's own server: BEA Economic Accounts

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

A remote MCP endpoint that gives an assistant access to HRSA data on health professional shortage areas and community health centers.

What you can do
The manifest lists no tools, so the exact operations are not documented. Based on the registry description, the server is meant to surface HRSA health resources data: health professional shortage area designations and community health center information. An assistant could use it to look up or reference these datasets when answering questions about US health workforce shortages or federally supported clinics.
When to use it
Use it when you need an assistant to reference HRSA shortage-area or community health center information, for example in public health, healthcare access, or site-planning questions.
Requirements
A remote MCP connection to the provider's endpoint; no packages, environment variables, headers, or authentication are declared.
Before you install
No tools, authentication, or data-handling details are documented, so what the server returns and whether it sends queries to third parties cannot be verified from the listing.

Installation

In SourceWeft

  1. Open HRSA Health Resources in the dashboard and add it to a workspace.
  2. 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.olyport%2Fhrsa/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.

{
  "mcpServers": {
    "hrsa-health-resources": {
      "type": "http",
      "url": "https://mcp.olyport.com/hrsa/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 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 listedRequired15 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 Olyport integrations