
AgentNX
io.github.IamWi11Published by GitHub account IamWi11v1.0.0Updated Oct 24, 2026
AI agents for federal IT & pharma: alert triage, ICAM, helpdesk, incidents, ticket routing.
Overview
Remote MCP endpoint offering AI agents for federal IT and pharma operations: alert triage, ICAM, helpdesk, incidents and ticket routing.
- What you can do
- Alert triage: hand operational alerts to agents for assessment and prioritization.
- Identity and access (ICAM): work with identity, credential and access management tasks.
- Helpdesk and incidents: route and handle support tickets and incident records.
- Ticket routing: direct incoming tickets to the right queue or owner.
- No tool list is published, so exact actions and inputs are not documented.
- When to use it
- Consider it when an assistant needs to help with IT operations in federal or pharmaceutical environments, such as triaging alerts, handling helpdesk requests, managing incidents or routing tickets.
- Requirements
- A remote MCP endpoint at the provider's site, reachable over the network. A bearer token API key is required and sent in the Authorization header; the provider says to request one through its demo page or by email.
Installation
In SourceWeft
- Open AgentNX in the dashboard and add it to a workspace.
- Connect Authorization token credentials. They are stored privately and never shown on public pages.
- 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/io.github.IamWi11%2Fagentnx/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.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"agentnx": {
"type": "http",
"url": "https://www.agentnx.ai/api/mcp-server",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
39% 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
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- 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.