pac-proxy-agent 9.x

Use pac-proxy-agent@^9.0.0 as an ESM Node.js HTTP Agent backed by a PAC file or PAC URI.

For

pac-proxy-agent@9.1.0

Verified

2026-09-08, 2 examples executed

Package

@modootoday/pmcp-pac-proxy-agent@9.0.0

What it covers

• Scope and runtime
• Constructor
• Resolving a PAC file without making a request
• Static protocol list
• Common mistakes
• What this skill does not cover

One example from this skill

This is the skill's own text, not a summary of it. It runs: that is what verifying means here.

import assert from 'node:assert/strict';
import { PacProxyAgent } from 'pac-proxy-agent';

const pac = `
function FindProxyForURL(url, host) {
  if (host === 'internal.example') return 'DIRECT';
  return 'PROXY proxy.example:8080';
}
`;

const agent = new PacProxyAgent(
  `pac+data:text/plain,${encodeURIComponent(pac)}`
);

const resolver = await agent.getResolver();
assert.equal(await resolver('http://internal.example/', 'internal.example'), 'DIRECT');
assert.equal(
  await resolver('http://external.example/', 'external.example'),
  'PROXY proxy.example:8080'
);

What it did in the sandbox

Verifying this skill meant installing the package and running code against it with no route out. Nothing was observed. The full ledger lists every package examined, including the ones that never became a skill.

Nothing observed is not a finding of safety. It means one run, under one policy, produced nothing to report.

Getting it

With a subscription:

npx -y @modootoday/pmcp login
npx -y @modootoday/pmcp install @modootoday/pmcp-pac-proxy-agent

It installs as a dev dependency of your project, and the MCP server finds it there like any other skill.